CVE-2026-64324
CVE CVE-2026-64324EUVD EUVD-2026-48868Published 2026-07-25T08:49:52.000ZLast changed 2026-08-05T12:41:01.000ZCVSS 7.8
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 5.15.165 <5.15.212; 6.1.105 <6.1.178; 934f815345c09c290a9b9a9cfdddc203ec2117e8 <fdd6229d2ae9914c1f25d1041db0f4f312a4fa76; 5def895b42ef16a2da6402818cba8d7ec8ede1ef; 56e69e59751d20993f243fb7dd6991c4e522424c <335202ab25b01fdd45889ff25eab70864686dea3; patch: 6.18.39; patch: 7.2-rc1; 56e69e59751d20993f243fb7dd6991c4e522424c <be87de7789a82a030a4896bc7683415ec9fa6f2b; patch: 6.12.96; patch: 7.1.4; 6.10.5 <6.11; 7c4fa9ebfce69619d132fe703dc2e2cf62a13723 <12af328d2ee8d68e81ba612246d0b54b22d23e1f; patch: 5.15.212; 4.19.320 <4.20; 5cc9745e2ea11aef7d5c9a42bc36f6cd3e1b4cc3 <fb49099206c5c57af28a157249fa7bcb5518f99e; 6.6.46 <6.6.145; 56e69e59751d20993f243fb7dd6991c4e522424c <5f0419457f89dce1a3f1c8e62a3adf2f39ab8168; patch: 6.6.145; 097420e48e30f51e8f4f650b5c946f5af63ec1a3; patch: 6.1.178; 05fb2bf477d3fe5421bd4cb699574737f52bd88b; 6.11; 5.10.224 <5.10.261; 22cc7323f090646c8cfb5939e6f15bdc2ed3fd27 <b54aee5652fcd7c23a0904a4623ec462c3edc70c; patch: 5.10.261; 5.4.282 <5.5; 56e69e59751d20993f243fb7dd6991c4e522424c <9442d75429b0c556292a7454fe888d54259f5240; patch: 0
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.