libceph: Fix potential out-of-bounds access in crush_decode()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f24e9980eb860d8600cbe5ef3d2fd9295320d229 · < 0f3604cbe4df14c5e58288ac9f57511e726a222d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
libceph: Fix potential out-of-bounds access in crush_decode()
A message of type CEPH_MSG_OSD_MAP containing a crush map with at least one bucket has two fields holding the bucket algorithm. If the values in these two fields differ, an out-of-bounds access can occur. This is the case because the first algorithm field (alg) is used to allocate the correct amount of memory for a bucket of this type, while the second algorithm field inside the bucket (b->alg) is used in the subsequent processing.
This patch fixes the issue by adding a check that compares alg and b->alg and aborts the processing in case they differ. Furthermore, b->alg is set to 0 in this case, because the destruction of the crush map also uses this field to determine the bucket type, which can again result in an out-of-bounds access when trying to free the memory pointed to by the fields of the bucket. To correctly free the memory allocated for the bucket in such a case, the corresponding call to kfree is moved from the algorithm-specific crush_destroy_bucket functions to the generic crush_destroy_bucket().
From the CVE record · Linux
The Linux kernel's libceph crush_decode() can access memory out of bounds when a CEPH_MSG_OSD_MAP message contains a crush map with at least one bucket and conflicting bucket algorithm fields. A crafted message meeting those conditions can trigger the access; the input does not specify authentication or user-interaction requirements.
Engineers running the Linux kernel with libceph should check their installations; affected versions are not specified.