Answer in brief
CVE-2026-52955 records a Critical severity (CVSS 9.8) vulnerability in libceph: Fix potential out-of-bounds access in crush_decode(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-52955 records a Critical severity (CVSS 9.8) vulnerability in libceph: Fix potential out-of-bounds access in crush_decode(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f24e9980eb860d8600cbe5ef3d2fd9295320d229 <6e70ef53e818c53eab28d7b0026b7fd03dddaba5 || >=f24e9980eb860d8600cbe5ef3d2fd9295320d229 <ebe76d58a48a48031b98543d86c4cd30a825b622 || >=f24e9980eb860d8600cbe5ef3d2fd9295320d229 <3f42508191e129ee6b5ea96578d5cab14f2a013a || >=f24e9980eb860d8600cbe5ef3d2fd9295320d229 <ea0d42137f0c06da71e37ffc647aab4c5309599a || >=f24e9980eb860d8600cbe5ef3d2fd9295320d229 <cceb10023e76bc89f3fe9238ebd0ccab0fc7c7c5 || >=f24e9980eb860d8600cbe5ef3d2fd9295320d229 <0f3604cbe4df14c5e58288ac9f57511e726a222d || >=f24e9980eb860d8600cbe5ef3d2fd9295320d229 <fb176a99e4c1a5a8448a83d83d3606203ba81faa || >=f24e9980eb860d8600cbe5ef3d2fd9295320d229 <4c79fc2d598694bda845b46229c9d48b65042970 | 6e70ef53e818c53eab28d7b0026b7fd03dddaba5, ebe76d58a48a48031b98543d86c4cd30a825b622, 3f42508191e129ee6b5ea96578d5cab14f2a013a, ea0d42137f0c06da71e37ffc647aab4c5309599a, cceb10023e76bc89f3fe9238ebd0ccab0fc7c7c5, 0f3604cbe4df14c5e58288ac9f57511e726a222d, fb176a99e4c1a5a8448a83d83d3606203ba81faa, 4c79fc2d598694bda845b46229c9d48b65042970 |
| Linux/Linuxgeneric | 2.6.34 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
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().
Quoted source text, attributed separately from HOL analysis.
CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f24e9980eb860d8600cbe5ef3d2fd9295320d229 <6e70ef53e818c53eab28d7b0026b7fd03dddaba5 || >=f24e9980eb860d8600cbe5ef3d2fd9295320d229 <ebe76d58a48a48031b98543d86c4cd30a825b622 || >=f24e9980eb860d8600cbe5ef3d2fd9295320d229 <3f42508191e129ee6b5ea96578d5cab14f2a013a || >=f24e9980eb860d8600cbe5ef3d2fd9295320d229 <ea0d42137f0c06da71e37ffc647aab4c5309599a || >=f24e9980eb860d8600cbe5ef3d2fd9295320d229 <cceb10023e76bc89f3fe9238ebd0ccab0fc7c7c5 || >=f24e9980eb860d8600cbe5ef3d2fd9295320d229 <0f3604cbe4df14c5e58288ac9f57511e726a222d || >=f24e9980eb860d8600cbe5ef3d2fd9295320d229 <fb176a99e4c1a5a8448a83d83d3606203ba81faa || >=f24e9980eb860d8600cbe5ef3d2fd9295320d229 <4c79fc2d598694bda845b46229c9d48b65042970 | 6e70ef53e818c53eab28d7b0026b7fd03dddaba5, ebe76d58a48a48031b98543d86c4cd30a825b622, 3f42508191e129ee6b5ea96578d5cab14f2a013a, ea0d42137f0c06da71e37ffc647aab4c5309599a, cceb10023e76bc89f3fe9238ebd0ccab0fc7c7c5, 0f3604cbe4df14c5e58288ac9f57511e726a222d, fb176a99e4c1a5a8448a83d83d3606203ba81faa, 4c79fc2d598694bda845b46229c9d48b65042970 |
| Linux/Linuxgeneric | 2.6.34 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
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().
Quoted source text, attributed separately from HOL analysis.