CVE-2026-99476
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().
Properties
- Severity
- HIGH
- Nvd fetched at
- 2026-11-22T12:30:49.958423+00:00
- Cvss severity
- HIGH
- Cvss score
- 7
- Epss score
- 0.00156
- Retrieved at
- 2026-11-22T12:32:29+00:00
- Last source
- FIRST EPSS
- Score
- 7
- Cvss version
- 3.1
- Cve id
- CVE-2026-99476
- Cvss vector
- CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- First seen by Signal
- 2026-11-19T15:26:52+00:00
- Name
- CVE-2026-99476
- Vector
- CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published at
- 2026-11-19T15:18:02.143
- Last modified
- 2026-11-22T11:16:53.593
- Epss percentile
- 0.04735
Related research
Explore deeper with Ninja Signal's threat intelligence graph