Skip to main content
VulnerabilityPublished

CVE-2026-99575: Linux kernel · f2fs: return -EIO for a lost inode block after cp_error

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in 9960426b20021e2a92916f7836b53ca53f4deeee : update Linux kernel when convenient.

Data as of 20 Nov 2026, 06:19 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 9960426b20021e2a92916f7836b53ca53f4deeee, 935bcf17f7052198a3ec82c55642c8e58f3a483c, 86dfdf4f2aeaf68905e9b08752d72624a05dd471 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to 9960426b20021e2a92916f7836b53ca53f4deeee, 935bcf17f7052198a3ec82c55642c8e58f3a483c, 86dfdf4f2aeaf68905e9b08752d72624a05dd471 or 53b12b63304b34a3850a901c4de3cc6ad08e0aee.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 28607bf3aa6f9762b32dc7f1ed0488823c0651b8, < 9960426b20021e2a92916f7836b53ca53f4deeee
Fixed in
  • 9960426b20021e2a92916f7836b53ca53f4deeee
LinuxLinuxAffected
  • ≥ 28607bf3aa6f9762b32dc7f1ed0488823c0651b8, < 935bcf17f7052198a3ec82c55642c8e58f3a483c
Fixed in
  • 935bcf17f7052198a3ec82c55642c8e58f3a483c
LinuxLinuxAffected
  • ≥ 28607bf3aa6f9762b32dc7f1ed0488823c0651b8, < 86dfdf4f2aeaf68905e9b08752d72624a05dd471
Fixed in
  • 86dfdf4f2aeaf68905e9b08752d72624a05dd471
LinuxLinuxAffected
  • ≥ 28607bf3aa6f9762b32dc7f1ed0488823c0651b8, < 53b12b63304b34a3850a901c4de3cc6ad08e0aee
Fixed in
  • 53b12b63304b34a3850a901c4de3cc6ad08e0aee
LinuxLinuxAffected
  • =5.14
Fixed in–

Description

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.

References

Community reviews

Loading reviews…