PT-2026-152455
CVE-2026-99575
·
Published
2026-11-20
·
Updated
2026-11-20
Description by
Score
N/A
Not availableNo 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: return -EIO for a lost inode block after cp error
After cp error, dirty node caches are dropped without being written.
If such an inode was never written, its NAT entry is still NEW ADDR,
and reading its inode block returns -ENOENT.
f2fs get dnode of data() 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 cp error or shutdown. A missing direct or indirect node is still
reported as -ENOENT.
Found an issue in the description? Have something to add? Feel free to write us 👾