CVE-2026-64323

udf: validate VAT header length against the VAT inode size

HIGH
7.1
CVSS Score
Published: July 25, 2026 at 08:49 AM UTC
Updated: October 19, 2026 at 09:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.1
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: udf: validate VAT header length against the VAT inode size udf_load_vat() takes the virtual partition's start offset straight from the on-disk VAT 2.0 header without checking it against the VAT inode size: map->s_type_specific.s_virtual.s_start_offset = le16_to_cpu(vat20->lengthHeader); map->s_type_specific.s_virtual.s_num_entries = (sbi->s_vat_inode->i_size - map->s_type_specific.s_virtual.s_start_offset) >> 2; lengthHeader is a fully attacker-controlled 16-bit value. If it exceeds the VAT inode size, the s_num_entries subtraction underflows to a huge count, which defeats the "block > s_num_entries" bound in udf_get_pblock_virt15(); and on the ICB-inline path that function reads ((__le32 *)(iinfo->i_data + s_start_offset))[block] so a large s_start_offset indexes past the inode's in-ICB data. Mounting a crafted UDF image with a virtual (VAT) partition then triggers an out-of-bounds read. Reject a VAT whose header length does not leave room for at least one entry within the VAT inode.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.26 ≤ v < 5.10.2615.11 ≤ v < 5.15.2125.16 ≤ v < 6.1.1786.13 ≤ v < 6.18.396.19 ≤ v < 7.1.46.2 ≤ v < 6.6.1456.7 ≤ v < 6.12.962.6.26fa5e08156335d0687c85b4e724db9448fb166601
Vendor states this is fixed in 0ad2d09a8d66fa8dc6f9b70d660b5fb4478ea934 (fixed)
Vendor states this is fixed in 2900e02a0dd4fc30ac9840e7ce4ca0b041ab0d63 (fixed)
Vendor states this is fixed in 55287a3555ff0515b3aff181d2c08c0462a41709 (fixed)
Vendor states this is fixed in 74580fdf022909e184223cacc364feb826982d96 (fixed)
Vendor states this is fixed in 883962731420ec271ed8c1cd76524f4b17faa982 (fixed)
Vendor states this is fixed in bb0d384c1f42a5b7ace0bd88fee80b9bb1d49acb (fixed)
Vendor states this is fixed in d8202786b3d75125c84ebc4de6d946f92fde0ee8 (fixed)
Vendor states this is fixed in e610fb113cdfa8bf4247c9bf4f2337b81ad4ddad (fixed)
Vendor states this is fixed in 2.6.26 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.96 (unaffected)
Vendor states this is fixed in 6.18.39 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.4 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.1HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-787CWE-125

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card