CVE-2026-52958: Linux kernel · libceph: Fix potential out-of-bounds access in osdmap_decode()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical · fixed in ee933694645dac062d65fc2743f92bc06fa0db6b : patch Linux kernel as a priority.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers can reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in ee933694645dac062d65fc2743f92bc06fa0db6b, e7187f33c02488697ec0d01d82bf7a3f8deaba8f, 8713bbc4b2b9ad78f803978e54b7e49dd21bd9be +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: libceph: Fix potential out-of-bounds access in osdmap_decode() When decoding osd_state and osd_weight from an incoming osdmap in osdmap_decode(), both are decoded for each osd, i.e., map->max_osd times. The ceph_decode_need() check only accounts for sizeof(*map->osd_weight) once. This can potentially result in an out-of-bounds memory access if the incoming message is corrupted such that the max_osd value exceeds the actual content of the osdmap message. This patch fixes the issue by changing the corresponding part in the ceph_decode_need() check to account for map->max_osd*sizeof(*map->osd_weight).
References
- git.kernel.org/stable/c/36a79759a288961b1ff28a68ec2d1f56f6848098 (opens in a new tab)
- git.kernel.org/stable/c/3f2575bb7f955d42569d96c3e04fa958a0dcf4b4 (opens in a new tab)
- git.kernel.org/stable/c/8713bbc4b2b9ad78f803978e54b7e49dd21bd9be (opens in a new tab)
- git.kernel.org/stable/c/0d2dd7e6bb74fd7712aa73457a4a821906c6863a (opens in a new tab)
- git.kernel.org/stable/c/e7187f33c02488697ec0d01d82bf7a3f8deaba8f (opens in a new tab)
- git.kernel.org/stable/c/48df98d12b15360cd56af5c1f460307b340c1197 (opens in a new tab)
- git.kernel.org/stable/c/ee933694645dac062d65fc2743f92bc06fa0db6b (opens in a new tab)
- git.kernel.org/stable/c/35d0ed82d03e5ee77ea4f31f20e29562a7721649 (opens in a new tab)