dm array: reject an array block whose value size is not the caller's
- 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.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, 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: total
Summary
In the Linux kernel, the following vulnerability has been resolved: dm array: reject an array block whose value size is not the caller's array_block_check() can only compare the header against itself, so a block with value_size 4 and max_entries 1018 is internally consistent and passes. dm-cache keeps two arrays -- mappings at 8 bytes and hints at 4 -- and the roots for both live in the superblock. Point the mappings root at a hint block and __load_mappings() walks it through an info whose value size is 8, so element_at() strides 8 bytes over 4-byte entries and reaches offset 8160 of a 4096-byte block. get_ablock() and __shadow_ablock() are the two places that hold the block and the caller at once. Reject there when the two value sizes disagree. Arrays only ever read their own blocks, so this fires on crafted metadata only.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 6513c29f44f2cc970c0e9fecfe5a6526c3e73025 · fixed in 35cd3b278448c79614f65ab6bbc9ed348d847df9; From 6513c29f44f2cc970c0e9fecfe5a6526c3e73025 · fixed in a8237cb8fa0a628d903e76635bfdeae4202036b9; From 6513c29f44f2cc970c0e9fecfe5a6526c3e73025 · fixed in a530a9a419a7c5fdb7dae55ffa2dd7a130631842; From 6513c29f44f2cc970c0e9fecfe5a6526c3e73025 · fixed in 522fa26da24ccaa298ebe3c1c97395d2d63dfc21; From 6513c29f44f2cc970c0e9fecfe5a6526c3e73025 · fixed in 7bf4b5cb42a4e27f36bcbc6209d82a5da9c0168c; From 6513c29f44f2cc970c0e9fecfe5a6526c3e73025 · fixed in ac4a5eb8b002a0742c938fc98b922e243f53573a; From 6513c29f44f2cc970c0e9fecfe5a6526c3e73025 · fixed in cb409b38b0232ee4385ef55cddcd6fbdd011a8a2; From 6513c29f44f2cc970c0e9fecfe5a6526c3e73025 · fixed in 4538a287bdf5d0f9a379c678e5262b9f5783f547
- Linux Linux
3.9
- KernelLinux
From 3.9.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.109; From 6.13.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4
References 8
git.kernel.org
- stable/c/35cd3b278448c79614f65ab6bbc9ed348d847df9
- stable/c/a8237cb8fa0a628d903e76635bfdeae4202036b9
- stable/c/a530a9a419a7c5fdb7dae55ffa2dd7a130631842
- stable/c/522fa26da24ccaa298ebe3c1c97395d2d63dfc21
- stable/c/7bf4b5cb42a4e27f36bcbc6209d82a5da9c0168c
- stable/c/ac4a5eb8b002a0742c938fc98b922e243f53573a
- stable/c/cb409b38b0232ee4385ef55cddcd6fbdd011a8a2
- stable/c/4538a287bdf5d0f9a379c678e5262b9f5783f547