CVE-2026-99575: f2fs: return -EIO for a lost inode block after cp_error
In the Linux kernel, the following vulnerability has been resolved:
f2fs: return -EIO for a lost inode block after cperror
After cperror, dirty node caches are dropped without being written. If such an inode was never written, its NAT entry is still NEWADDR, and reading its inode block returns -ENOENT.
f2fsgetdnodeofdata() passes that -ENOENT up, and callers take it as a hole. Since the inode block is missing, the next offset can only advance one block, so fiemap walks block by block up to maxbytes, about 2^30 blocks, while holding the inode lock. It took hours in a power-off recovery test after shutdown and blocked unlink and umount on the file.
Return -EIO instead of -ENOENT when the inode block itself is missing after cperror or shutdown. A missing direct or indirect node is still reported as -ENOENT.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5
Frequently Asked Questions
What conditions are required to trigger the prolonged fiemap walk?
The filesystem must have entered cp_error or shutdown, causing dirty node caches to be dropped before an inode block has ever been written. The affected inode retains a NEW_ADDR NAT entry, and a fiemap operation then encounters the missing inode block as -ENOENT and treats it as a hole.
What is the operational impact?
Fiemap can scan one block at a time up to maxbytes, roughly 2^30 blocks, while holding the inode lock. In the reported power-off recovery test this took hours and blocked unlink and unmount operations involving the file.
How does the fix change error handling?
When the inode block itself is missing after cp_error or shutdown, the fix returns -EIO rather than -ENOENT, preventing callers from interpreting the condition as a hole. Missing direct or indirect node blocks continue to return -ENOENT.