Data corruption via duplicate filesystem block freeing
Published Nov 20, 2026 · Updated Nov 20, 2026
Block-accounting corruption in Linux UDF allows local users to corrupt file data through preallocation cleanup on writable UDF filesystems. In udf_discard_prealloc(), an end-of-list peek overwrites the saved extent location and length, causing an empty allocation extent's block to be freed twice instead of releasing the preallocated blocks. Triggering requires file operations on a writable UDF mount with the relevant extent layout; unallocated space tables permit duplicate block allocation and corrupted reads, while space bitmaps leak preallocated blocks and miscount free space.
Summary
What happened
Block-accounting corruption in Linux UDF allows local users to corrupt file data through preallocation cleanup on writable UDF filesystems. In udf_discard_prealloc(), an end-of-list peek overwrites the saved extent location and length, causing an empty allocation extent's block to be freed twice instead of releasing the preallocated blocks. Triggering requires file operations on a writable UDF mount with the relevant extent layout; unallocated space tables permit duplicate block allocation and corrupted reads, while space bitmaps leak preallocated blocks and miscount free space.
The record
- CVE
- CVE-2026-99600
- Published
- Nov 20, 2026
- Updated
- Nov 20, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 20, 2026CVE publishedPublication date reported by the CVE source.
- Nov 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=12a88f572d6d94b5c0b72e2d1782cc2e96ac06cf
- Affected versionversion=1a075f4a549481ce6e8518d8379f193ccec6b746
- Affected versionversion=4.14.303 <4.15
- Affected versionversion=4.19.270 <4.20
- Affected versionversion=4.9.337 <4.10
- Affected versionversion=4d835efd561dfb9bf5409f11f4ecd428d5d29226
- Affected versionversion=5.10.161 <5.11
- Affected versionversion=5.15.85 <5.16
- Affected versionversion=5.4.229 <5.5
- Affected versionversion=6.0.15 <6.1
- Affected versionversion=6.1.1 <6.2
- Affected versionversion=6.2
- Affected versionversion=63dbbd8f1499b0a161e701a04aa50148d60bd1f7
- Affected versionversion=72f651c96c8aadf087fd782d551bf7db648a8c2e
- Affected versionversion=7665857f88557c372da35534165721156756f77f
- Affected versionversion=ae56d9a017724f130cf1a263dd82a78d2a6e3852
- Affected versionversion=c8b6fa4511a7900db9fb0353b630d4d2ed1ba99c
- Affected versionversion=cfe4c1b25dd6d2f056afc00b7c98bcb3dd0b1fc3 <0c52750caaaccee8b0e929450fe6538ec4985722
- Affected versionversion=cfe4c1b25dd6d2f056afc00b7c98bcb3dd0b1fc3 <0efa27a0d8b8f4b75eed80728d2c331c6104c308
- Affected versionversion=cfe4c1b25dd6d2f056afc00b7c98bcb3dd0b1fc3 <4ef0ffc5da8d2966d8f4bd0b6dc88a6fab2e891c
- Affected versionversion=cfe4c1b25dd6d2f056afc00b7c98bcb3dd0b1fc3 <f7d6f3fed104ca7e48a9ed081c2047300d3f96fc
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
- Upstream UDF preallocation corruption reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us