Answer in brief
CVE-2026-64324 records a High severity (CVSS 7.8) vulnerability in udf: validate free block extents against the partition length. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=934f815345c09c290a9b9a9cfdddc203ec2117e8 <fdd6229d2ae9914c1f25d1041db0f4f312a4fa76 || >=22cc7323f090646c8cfb5939e6f15bdc2ed3fd27 <b54aee5652fcd7c23a0904a4623ec462c3edc70c || >=7c4fa9ebfce69619d132fe703dc2e2cf62a13723 <12af328d2ee8d68e81ba612246d0b54b22d23e1f || >=5cc9745e2ea11aef7d5c9a42bc36f6cd3e1b4cc3 <fb49099206c5c57af28a157249fa7bcb5518f99e || >=56e69e59751d20993f243fb7dd6991c4e522424c <9442d75429b0c556292a7454fe888d54259f5240 || >=56e69e59751d20993f243fb7dd6991c4e522424c <335202ab25b01fdd45889ff25eab70864686dea3 || >=56e69e59751d20993f243fb7dd6991c4e522424c <be87de7789a82a030a4896bc7683415ec9fa6f2b || >=56e69e59751d20993f243fb7dd6991c4e522424c <5f0419457f89dce1a3f1c8e62a3adf2f39ab8168 || 097420e48e30f51e8f4f650b5c946f5af63ec1a3 || 5def895b42ef16a2da6402818cba8d7ec8ede1ef || 05fb2bf477d3fe5421bd4cb699574737f52bd88b || >=5.10.224 <5.10.261 || >=5.15.165 <5.15.212 || >=6.1.105 <6.1.178 || >=6.6.46 <6.6.145 || >=4.19.320 <4.20 || >=5.4.282 <5.5 || >=6.10.5 <6.11 | fdd6229d2ae9914c1f25d1041db0f4f312a4fa76, b54aee5652fcd7c23a0904a4623ec462c3edc70c, 12af328d2ee8d68e81ba612246d0b54b22d23e1f, fb49099206c5c57af28a157249fa7bcb5518f99e, 9442d75429b0c556292a7454fe888d54259f5240, 335202ab25b01fdd45889ff25eab70864686dea3, be87de7789a82a030a4896bc7683415ec9fa6f2b, 5f0419457f89dce1a3f1c8e62a3adf2f39ab8168, 5.10.261, 5.15.212, 6.1.178, 6.6.145, 4.20, 5.5, 6.11 |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: udf: validate free block extents against the partition length udf_free_blocks() checks the logical block number and count against the partition length, but drops the extent offset from that final bound. A crafted extent can pass the guard while logicalBlockNum + offset + count points past the partition, which later indexes past the space bitmap array. A single ftruncate(2) on a file backed by such an extent reliably panics the kernel. This is a local availability issue. On desktop systems where UDisks/polkit allows the active user to mount removable UDF media without CAP_SYS_ADMIN, an unprivileged local user can supply the crafted filesystem and trigger the panic by truncating a writable file on it. Systems that require root or CAP_SYS_ADMIN to mount the image have a higher prerequisite. No confidentiality or integrity impact is claimed: the reproduced primitive is an out-of-bounds read of a bitmap pointer slot followed by a kernel panic. Use the already computed logicalBlockNum + offset + count value for the partition length check. Also make load_block_bitmap() reject an out-of-range block group before indexing s_block_bitmap[], so corrupted callers cannot walk past the flexible array.
Quoted source text, attributed separately from HOL analysis.