CVE-2026-99575
In the Linux kernel, the following vulnerability has been resolved: …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/53b12b63304b34a3850a901c4de3cc6ad08e0aee
- git.kernel.org/stable/c/86dfdf4f2aeaf68905e9b08752d72624a05dd471
- git.kernel.org/stable/c/935bcf17f7052198a3ec82c55642c8e58f3a483c
- git.kernel.org/stable/c/9960426b20021e2a92916f7836b53ca53f4deeee
- nvd.nist.gov/vuln/detail/CVE-2026-99575
- cve.org/CVERecord?id=CVE-2026-99575
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.