CVE-2026-99569
Severity unknownNo known exploitationFix availablef2fs: release a removed xattr node in roll-forward recovery
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 6% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
In the Linux kernel, the following vulnerability has been resolved: f2fs: release a removed xattr node in roll-forward recovery When xattrs shrink enough to fit in the inline xattr area, write_all_xattrs() truncates the xattr node and clears i_xattr_nid. If the file is then fsynced without a checkpoint, only the inode block is written, with i_xattr_nid of 0. Roll-forward recovery starts from the checkpointed inode, whose i_xattr_nid still points to the old xattr node. f2fs_recover_inline_xattr() copies only the inline xattr area, and f2fs_update_inode() writes the old i_xattr_nid back. So the inode keeps the stale xattr node: - The node block is never released, and fsck reports "nonzero bytes in xattr space after end of list". - If the inline xattr list ends exactly at the end of the inline area, its terminator is read from the stale node, and the removed xattrs come back after recovery. When the fsynced inode has no xattr node but the checkpointed one has, release the old xattr node as truncate_node() does: check its block address, invalidate the block and drop its node cache, which may still be dirty.
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Linux))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from 28cdce0459ccea71ea734d7903d39910d1c6a05d before c06cfda3b67692651438876663ae7cdc187eb214 | c06cfda3b67692651438876663ae7cdc187eb214 | CVE Program |
| Linux | Linux | from 28cdce0459ccea71ea734d7903d39910d1c6a05d before 6d9c89d6dd18c0cfec33bdb468bf4b86c0ca7cea | 6d9c89d6dd18c0cfec33bdb468bf4b86c0ca7cea | CVE Program |
| Linux | Linux | from 28cdce0459ccea71ea734d7903d39910d1c6a05d before f5924de8867c09206ba631b9faed63862ec00a10 | f5924de8867c09206ba631b9faed63862ec00a10 | CVE Program |
| Linux | Linux | from 28cdce0459ccea71ea734d7903d39910d1c6a05d before 246a50b23bf2042c77b167272db121d03c8dd473 | 246a50b23bf2042c77b167272db121d03c8dd473 | CVE Program |
| Linux | Linux | 3.15 | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.12.118 up to and including 6.12.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.64 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.3.5 up to and including 7.3.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.4-rc1 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 3.15 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Linux)
Vendor guidance and references
- https://git.kernel.org/stable/c/246a50b23bf2042c77b167272db121d03c8dd473 (opens in a new tab)
- https://git.kernel.org/stable/c/6d9c89d6dd18c0cfec33bdb468bf4b86c0ca7cea (opens in a new tab)
- https://git.kernel.org/stable/c/c06cfda3b67692651438876663ae7cdc187eb214 (opens in a new tab)
- https://git.kernel.org/stable/c/f5924de8867c09206ba631b9faed63862ec00a10 (opens in a new tab)