CVE-2026-99575
What it is
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.
At a glance
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: not scored yet.
- Severity: not scored yet.
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Record status
- Received
Affected
- Linux < 9960426b20021e2a92916f7836b53ca53f4deeee
- Linux < 935bcf17f7052198a3ec82c55642c8e58f3a483c
- Linux < 86dfdf4f2aeaf68905e9b08752d72624a05dd471
- Linux < 53b12b63304b34a3850a901c4de3cc6ad08e0aee
- Linux 5.14
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-99575.md and follow it. Check whether this project is affected by CVE-2026-99575. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.