CVE-2026-99476: Linux kernel · fsverity: Set S_VERITY only after rollback is no longer possible
Source GCVE Database
Not known to be exploited : upgrade to c349b233d6ab0fc3517401a1e2d36f5f90eb8c9b or 10c13801ea38e4ced23c59052ce45acb07c5deda when convenient.
Data as of 19 Nov 2026, 17:04 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in c349b233d6ab0fc3517401a1e2d36f5f90eb8c9b, 10c13801ea38e4ced23c59052ce45acb07c5deda
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade Linux kernel to c349b233d6ab0fc3517401a1e2d36f5f90eb8c9b or 10c13801ea38e4ced23c59052ce45acb07c5deda.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel to address this issue by changing when S_VERITY is set and improving rollback handling. Users should update to the fixed kernel versions once available.
Description
A use-after-free vulnerability in the Linux kernel's fsverity feature was fixed by ensuring the S_VERITY flag is set only after rollback is no longer possible in ext4 and btrfs filesystems. This prevents premature verification enabling that could lead to memory safety issues.