udf: validate VAT header length against the VAT inode size
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From fa5e08156335d0687c85b4e724db9448fb166601 · fixed in 0ad2d09a8d66fa8dc6f9b70d660b5fb4478ea934; From fa5e08156335d0687c85b4e724db9448fb166601 · fixed in 883962731420ec271ed8c1cd76524f4b17faa982; From fa5e08156335d0687c85b4e724db9448fb166601 · fixed in 2900e02a0dd4fc30ac9840e7ce4ca0b041ab0d63; From fa5e08156335d0687c85b4e724db9448fb166601 · fixed in bb0d384c1f42a5b7ace0bd88fee80b9bb1d49acb; From fa5e08156335d0687c85b4e724db9448fb166601 · fixed in 55287a3555ff0515b3aff181d2c08c0462a41709; From fa5e08156335d0687c85b4e724db9448fb166601 · fixed in e610fb113cdfa8bf4247c9bf4f2337b81ad4ddad; From fa5e08156335d0687c85b4e724db9448fb166601 · fixed in 74580fdf022909e184223cacc364feb826982d96; From fa5e08156335d0687c85b4e724db9448fb166601 · fixed in d8202786b3d75125c84ebc4de6d946f92fde0ee8
- Linux Linux
2.6.26
- KernelLinux
From 2.6.26 · fixed in 5.10.261; From 5.11.0 · fixed in 5.15.212; From 5.16.0 · fixed in 6.1.178; From 6.2.0 · fixed in 6.6.145; From 6.7.0 · fixed in 6.12.96; From 6.13.0 · fixed in 6.18.39; From 6.19.0 · fixed in 7.1.4
References 8
git.kernel.org
- stable/c/0ad2d09a8d66fa8dc6f9b70d660b5fb4478ea934
- stable/c/883962731420ec271ed8c1cd76524f4b17faa982
- stable/c/2900e02a0dd4fc30ac9840e7ce4ca0b041ab0d63
- stable/c/bb0d384c1f42a5b7ace0bd88fee80b9bb1d49acb
- stable/c/55287a3555ff0515b3aff181d2c08c0462a41709
- stable/c/e610fb113cdfa8bf4247c9bf4f2337b81ad4ddad
- stable/c/74580fdf022909e184223cacc364feb826982d96
- stable/c/d8202786b3d75125c84ebc4de6d946f92fde0ee8