Skip to main content
VulnerabilityPublished

CVE-2026-99569: Linux kernel · f2fs: release a removed xattr node in roll-forward recovery

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99569· Medium

Not known to be exploited · fixed in f5924de8867c09206ba631b9faed63862ec00a10 : update Linux kernel when convenient.

Data as of 20 Nov 2026, 07:34 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in f5924de8867c09206ba631b9faed63862ec00a10, c06cfda3b67692651438876663ae7cdc187eb214, 246a50b23bf2042c77b167272db121d03c8dd473 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 19 Nov 2026.

What to do

Upgrade Linux kernel to f5924de8867c09206ba631b9faed63862ec00a10, c06cfda3b67692651438876663ae7cdc187eb214, 246a50b23bf2042c77b167272db121d03c8dd473 or 6d9c89d6dd18c0cfec33bdb468bf4b86c0ca7cea.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 28cdce0459ccea71ea734d7903d39910d1c6a05d, < f5924de8867c09206ba631b9faed63862ec00a10
Fixed in
  • f5924de8867c09206ba631b9faed63862ec00a10
LinuxLinuxAffected
  • ≥ 28cdce0459ccea71ea734d7903d39910d1c6a05d, < c06cfda3b67692651438876663ae7cdc187eb214
Fixed in
  • c06cfda3b67692651438876663ae7cdc187eb214
LinuxLinuxAffected
  • ≥ 28cdce0459ccea71ea734d7903d39910d1c6a05d, < 246a50b23bf2042c77b167272db121d03c8dd473
Fixed in
  • 246a50b23bf2042c77b167272db121d03c8dd473
LinuxLinuxAffected
  • ≥ 28cdce0459ccea71ea734d7903d39910d1c6a05d, < 6d9c89d6dd18c0cfec33bdb468bf4b86c0ca7cea
Fixed in
  • 6d9c89d6dd18c0cfec33bdb468bf4b86c0ca7cea
LinuxLinuxAffected
  • =3.15
Fixed in–

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.

References

Community reviews

Loading reviews…