CVE-2026-52955

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-24. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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().

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
31.1%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 15, 2026

Advisory Details (10)

Auto-updated Jul 16, 2026
Patch available. Sources: redhat.
redhat

2492328 – (CVE-2026-52955) CVE-2026-52955 kernel: libceph: Fix potential out-of-bounds access in crush_decode()

https://bugzilla.redhat.com/show_bug.cgi?id=2492328
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-52955
generic

libceph: Fix potential out-of-bounds access in crush_decode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fb176a99e4c1a5a8448a83d83d3606203ba81faa
generic

libceph: Fix potential out-of-bounds access in crush_decode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ebe76d58a48a48031b98543d86c4cd30a825b622
generic

libceph: Fix potential out-of-bounds access in crush_decode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ea0d42137f0c06da71e37ffc647aab4c5309599a
generic

libceph: Fix potential out-of-bounds access in crush_decode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cceb10023e76bc89f3fe9238ebd0ccab0fc7c7c5
generic

libceph: Fix potential out-of-bounds access in crush_decode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6e70ef53e818c53eab28d7b0026b7fd03dddaba5
generic

libceph: Fix potential out-of-bounds access in crush_decode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4c79fc2d598694bda845b46229c9d48b65042970
generic

libceph: Fix potential out-of-bounds access in crush_decode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3f42508191e129ee6b5ea96578d5cab14f2a013a
generic

libceph: Fix potential out-of-bounds access in crush_decode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0f3604cbe4df14c5e58288ac9f57511e726a222d

Vendor Advisories for CVE-2026-52955(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 131× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 131 total refreshes for this CVE.

  1. 2026-07-23 03:19 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:25 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 02:29 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-17 05:15 UTCGHSA enrichment
  10. 2026-07-17 00:41 UTCGHSA enrichment
  11. 2026-07-16 20:15 UTCGHSA enrichment
  12. 2026-07-16 17:03 UTCEPSS rescore
  13. 2026-07-16 14:38 UTCGHSA enrichment
  14. 2026-07-16 10:14 UTCGHSA enrichment
  15. 2026-07-16 05:48 UTCGHSA enrichment
  16. 2026-07-16 01:24 UTCGHSA enrichment
  17. 2026-07-15 20:58 UTCGHSA enrichment
  18. 2026-07-15 16:57 UTCEPSS rescore
  19. 2026-07-15 16:57 UTCEPSS rescore
  20. 2026-07-15 16:26 UTCGHSA enrichment
  21. 2026-07-15 12:01 UTCGHSA enrichment
  22. 2026-07-15 07:26 UTCGHSA enrichment
  23. 2026-07-15 03:00 UTCGHSA enrichment
  24. 2026-07-15 02:00 UTCEPSS rescore
  25. 2026-07-15 02:00 UTCEPSS rescore
Show 75 more
  1. 2026-07-14 22:34 UTCGHSA enrichment
  2. 2026-07-14 18:10 UTCGHSA enrichment
  3. 2026-07-14 13:21 UTCGHSA enrichment
  4. 2026-07-14 08:57 UTCGHSA enrichment
  5. 2026-07-14 04:32 UTCGHSA enrichment
  6. 2026-07-14 00:07 UTCGHSA enrichment
  7. 2026-07-13 22:31 UTCEPSS rescore
  8. 2026-07-13 19:42 UTCGHSA enrichment
  9. 2026-07-13 15:16 UTCGHSA enrichment
  10. 2026-07-13 10:45 UTCGHSA enrichment
  11. 2026-07-13 06:18 UTCGHSA enrichment
  12. 2026-07-13 06:13 UTCEPSS rescore
  13. 2026-07-13 06:13 UTCEPSS rescore
  14. 2026-07-13 01:52 UTCGHSA enrichment
  15. 2026-07-12 21:28 UTCGHSA enrichment
  16. 2026-07-12 17:03 UTCGHSA enrichment
  17. 2026-07-12 12:38 UTCGHSA enrichment
  18. 2026-07-12 08:13 UTCGHSA enrichment
  19. 2026-07-12 05:46 UTCEPSS rescore
  20. 2026-07-12 03:49 UTCGHSA enrichment
  21. 2026-07-11 23:24 UTCGHSA enrichment
  22. 2026-07-11 18:59 UTCGHSA enrichment
  23. 2026-07-11 14:35 UTCGHSA enrichment
  24. 2026-07-11 10:07 UTCGHSA enrichment
  25. 2026-07-11 08:27 UTCEPSS rescore
  26. 2026-07-11 08:27 UTCEPSS rescore
  27. 2026-07-11 05:42 UTCGHSA enrichment
  28. 2026-07-11 01:18 UTCGHSA enrichment
  29. 2026-07-10 20:44 UTCGHSA enrichment
  30. 2026-07-10 16:20 UTCGHSA enrichment
  31. 2026-07-10 11:51 UTCGHSA enrichment
  32. 2026-07-10 07:17 UTCGHSA enrichment
  33. 2026-07-10 02:49 UTCGHSA enrichment
  34. 2026-07-09 22:12 UTCGHSA enrichment
  35. 2026-07-09 19:10 UTCEPSS rescore
  36. 2026-07-09 19:10 UTCEPSS rescore
  37. 2026-07-09 17:47 UTCGHSA enrichment
  38. 2026-07-09 13:13 UTCGHSA enrichment
  39. 2026-07-09 08:49 UTCGHSA enrichment
  40. 2026-07-09 04:24 UTCGHSA enrichment
  41. 2026-07-08 23:56 UTCGHSA enrichment
  42. 2026-07-08 19:31 UTCGHSA enrichment
  43. 2026-07-08 15:16 UTCEPSS rescore
  44. 2026-07-08 15:16 UTCEPSS rescore
  45. 2026-07-08 15:03 UTCGHSA enrichment
  46. 2026-07-08 10:37 UTCGHSA enrichment
  47. 2026-07-08 06:11 UTCGHSA enrichment
  48. 2026-07-08 01:44 UTCGHSA enrichment
  49. 2026-07-07 21:19 UTCGHSA enrichment
  50. 2026-07-07 16:55 UTCGHSA enrichment
  51. 2026-07-07 13:46 UTCEPSS rescore
  52. 2026-07-07 13:46 UTCEPSS rescore
  53. 2026-07-07 11:20 UTCGHSA enrichment
  54. 2026-07-07 06:56 UTCGHSA enrichment
  55. 2026-07-07 02:19 UTCGHSA enrichment
  56. 2026-07-06 21:49 UTCGHSA enrichment
  57. 2026-07-06 17:24 UTCGHSA enrichment
  58. 2026-07-06 16:27 UTCEPSS rescore
  59. 2026-07-06 16:27 UTCEPSS rescore
  60. 2026-07-06 12:52 UTCGHSA enrichment
  61. 2026-07-06 08:25 UTCGHSA enrichment
  62. 2026-07-06 03:58 UTCGHSA enrichment
  63. 2026-07-06 02:23 UTCEPSS rescore
  64. 2026-07-06 02:23 UTCEPSS rescore
  65. 2026-07-05 23:34 UTCGHSA enrichment
  66. 2026-07-05 19:09 UTCGHSA enrichment
  67. 2026-07-05 14:45 UTCGHSA enrichment
  68. 2026-07-05 10:10 UTCGHSA enrichment
  69. 2026-07-05 05:43 UTCGHSA enrichment
  70. 2026-07-05 02:30 UTCEPSS rescore
  71. 2026-07-05 01:16 UTCGHSA enrichment
  72. 2026-07-04 20:41 UTCGHSA enrichment
  73. 2026-07-04 16:16 UTCGHSA enrichment
  74. 2026-07-04 11:52 UTCGHSA enrichment
  75. 2026-07-04 07:28 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-52955?
CVE-2026-52955 is a critical vulnerability published on June 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 CEPHMSGOSD_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,…
When was CVE-2026-52955 disclosed?
CVE-2026-52955 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52955 actively exploited?
CVE-2026-52955 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 31.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52955?
CVE-2026-52955 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-52955?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52955, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-52955

Explore →

Is Your Infrastructure Affected by CVE-2026-52955?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.