libceph: reject zero bucket types in crush_decode
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f24e9980eb860d8600cbe5ef3d2fd9295320d229 · < 3b2f1937f5fce8b7dd5432e7693e3cc8b5eece56| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
libceph: reject zero bucket types in crush_decode
CRUSH bucket type 0 is reserved for devices. The mapper relies on that invariant and uses type 0 to identify leaf devices.
If crush_decode() accepts a bucket with type 0, a malformed CRUSH map can make the mapper treat a negative bucket ID as a device and pass it to is_out(), which then indexes the OSD weight array with a negative value.
Reject zero bucket types while decoding the CRUSH map so the invalid state never reaches the mapper.
From the CVE record · Linux
The Linux kernel's libceph CRUSH map decoder accepts a bucket type reserved for devices. A malformed CRUSH map can then cause the mapper to index the OSD weight array with a negative value. The input does not specify how an attacker could supply the map or whether authentication or user interaction is required.
Engineers running Linux kernels that use libceph should check their versions against the vendor advisory; affected versions are not specified.