Skip to main content
Menu
CVEs

Linux kernel double free of file blocks in UDF preallocation discard

CVE-2026-99600Published November 20, 2026, updated

Exploited
No known exploitation
Fix
Fixed in 4.10, 4.15, 4.20, 5.5, 5.11, and 3 more
Who is exposed
Not reported

Summary

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

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

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

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"}.

Affected versions

cve.now Index

20Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 6

Questions about CVE-2026-99600

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: cve.now feed data

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: cve.now feed data

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: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.