libceph: reject buckets with mismatched CRUSH ids
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 66a0e2d579dbec5c676cfe446234ffebb267c564 · < 00562ccd4e88d092b9b851df50fad20442bfeb24| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s libceph CRUSH decoder accepts buckets whose encoded IDs do not match their array slots. A malformed CRUSH map can make buckets share workspace, causing a four-byte out-of-bounds write during replica selection; the input does not establish an attack path or authentication requirements.
Engineers running Linux kernels with libceph should check whether their kernel includes the fix; affected versions are not specified.