PT-2026-151687
CVE-2026-99476
·
Published
2026-11-19
·
Updated
2026-11-19
Description by
Score
N/A
Not availableNo severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
In the Linux kernel, the following vulnerability has been resolved:
fsverity: Set S VERITY only after rollback is no longer possible
Commit f77f281b6118 ("fsverity: use a hashtable to find the
fsverity info") changed the implementation of FS IOC ENABLE VERITY to
make concurrent reads start going through fsverity verification slightly
earlier than they did before.
Instead of it happening when enable verity() calls fsverity set info(),
it now happens when ->end enable verity() sets S VERITY.
However, ext4 and btrfs can roll back verity after they set S VERITY,
causing a use-after-free.
Fix that by making ext4 and btrfs set S VERITY only after rollback is no
longer possible. On failure, don't roll back S VERITY, but do roll back
the filesystem-specific verity flag.
Also update enable verity() to handle any future instances of this bug
more safely by warning and not freeing the fsverity info.
Finally, tweak some comments. Clarify one, and move information from
another to its proper place in the comment for ->end enable verity().
Found an issue in the description? Have something to add? Feel free to write us 👾