libceph: reject buckets with mismatched CRUSH ids
- 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: yes
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: libceph: reject buckets with mismatched CRUSH ids crush_decode() stores bucket data by array slot, and the mapper later derives the per-bucket workspace index from the decoded bucket id. A malformed map can therefore make one bucket reuse another bucket's workspace by encoding an id different from -1 - slot. For uniform buckets, the second replica selection expands the source bucket's permutation into that aliased workspace buffer. If the source bucket is larger than the aliased bucket, the write runs past the smaller permutation array and can escape the kvmalloc'd CRUSH workspace. KASAN reports a slab OOB write of 4 bytes in bucket_perm_choose(). Reject buckets whose encoded id does not match their array slot. Valid CRUSH maps already use the canonical negative id corresponding to the bucket slot, so this restores the invariant expected by work->work[-1 - in->id] without changing valid map behavior.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 66a0e2d579dbec5c676cfe446234ffebb267c564 · fixed in ee59040d6ed1a5f8d10d27174b8f32c90ca8e89a; From 66a0e2d579dbec5c676cfe446234ffebb267c564 · fixed in baad5875fdd2f5e248250fc3519bb045d64f1716; From 66a0e2d579dbec5c676cfe446234ffebb267c564 · fixed in 4aeb93daadf388e72073abc204312dd364eeb30a; From 66a0e2d579dbec5c676cfe446234ffebb267c564 · fixed in 6e5c6ce252b1eccfd41670a5cf95ab44f7ba7022; From 66a0e2d579dbec5c676cfe446234ffebb267c564 · fixed in 3516a4131c4e45d62ee4e42e82c36930e8c1fbbd; From 66a0e2d579dbec5c676cfe446234ffebb267c564 · fixed in 00562ccd4e88d092b9b851df50fad20442bfeb24; From 66a0e2d579dbec5c676cfe446234ffebb267c564 · fixed in 79900d978158b2d80eef952fc41b9e4dc58d7b83; From 66a0e2d579dbec5c676cfe446234ffebb267c564 · fixed in 3cde4a8302301679937474a5f7a851394cc1bd11
- Linux Linux
4.11
- KernelLinux
From 4.11.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/ee59040d6ed1a5f8d10d27174b8f32c90ca8e89a
- stable/c/baad5875fdd2f5e248250fc3519bb045d64f1716
- stable/c/4aeb93daadf388e72073abc204312dd364eeb30a
- stable/c/6e5c6ce252b1eccfd41670a5cf95ab44f7ba7022
- stable/c/3516a4131c4e45d62ee4e42e82c36930e8c1fbbd
- stable/c/00562ccd4e88d092b9b851df50fad20442bfeb24
- stable/c/79900d978158b2d80eef952fc41b9e4dc58d7b83
- stable/c/3cde4a8302301679937474a5f7a851394cc1bd11