PT-2026-152449

CVE-2026-99569

·

Published

2026-11-20

·

Updated

2026-11-20

Description by

Score
N/A
Not available

No 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:
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.
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾