AZL-115291: CVE-2026-99569 affecting package kernel 6.6.161.1-1
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, writeallxattrs() truncates the xattr node and clears ixattrnid. If the file is then fsynced without a checkpoint, only the inode block is written, with ixattrnid of 0.
Roll-forward recovery starts from the checkpointed inode, whose ixattrnid still points to the old xattr node. f2fsrecoverinlinexattr() copies only the inline xattr area, and f2fsupdateinode() writes the old ixattrnid 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 truncatenode() does: check its block address, invalidate the block and drop its node cache, which may still be dirty.