CVE-2026-99575
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.
Properties
- Last source
- FIRST EPSS
- Nvd fetched at
- 2026-11-22T12:30:49.958423+00:00
- Epss score
- 0.00209
- Cve id
- CVE-2026-99575
- First seen by Signal
- 2026-11-20T07:38:10+00:00
- Name
- CVE-2026-99575
- Retrieved at
- 2026-11-22T12:32:29+00:00
- Published at
- 2026-11-20T06:17:48.577
- Last modified
- 2026-11-20T06:17:48.577
- Epss percentile
- 0.1104
Related research
Explore deeper with Ninja Signal's threat intelligence graph