CVE-2026-80558

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 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: Avoid using invalid osd indices from primary_temp

A corrupted osdmap received from a Ceph monitor or OSD may contain osd indices in its pg_temp, primary_temp, pg_upmap, and pg_upmap_items parts that don't exist, i.e., that are greater than max_osd or smaller than CEPH_HOMELESS_OSD (-1). These indices are used to create the up and acting set in ceph_pg_to_up_acting_osds(), called from calc_target(). While most of these osd indices are checked, the one from primary_temp is not. Subsequently, this may lead to calc_target() returning this (potentially invalid) index as target osd for a (linger) request. Because the osd_state, osd_weight, and osd_addr arrays only contain max_osd entries (with indices 0 to max_osd -1), this leads to out-of-bounds accesses when trying to read values from these arrays.

This patch fixes the issue by adding a check to get_temp_osds(), so that only valid osd indices from primary_temp are used, and it falls back to using the primary from pg_temp or the up set if it is invalid.

[ idryomov: changelog ]

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%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

August 26, 2026

Last Modified

August 27, 2026

Advisory Details (6)

Auto-updated Aug 27, 2026
No patch confirmed yet.
generic

libceph: Avoid using invalid osd indices from primary_temp - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: Avoid using invalid osd indices from primary_temp - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: Avoid using invalid osd indices from primary_temp - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/505fc50b8ff8e687b7e3ef6866269dea27366224
generic

libceph: Avoid using invalid osd indices from primary_temp - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: Avoid using invalid osd indices from primary_temp - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3660b98d1204b419f6a77e9a295f148dcf38d042
generic

libceph: Avoid using invalid osd indices from primary_temp - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1c705fe8e59c6b16f48964973fb23c8ec4735b73

Vendor Advisories for CVE-2026-80558(1)

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

Data Freshness Timeline

(refreshed 27× in last 7d / 27× 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.

  1. 2026-08-30 02:00 UTCEG score recompute
  2. 2026-08-30 02:00 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 21:42 UTCGHSA enrichment
  5. 2026-08-29 17:23 UTCGHSA enrichment
  6. 2026-08-29 13:02 UTCGHSA enrichment
  7. 2026-08-29 08:39 UTCGHSA enrichment
  8. 2026-08-29 04:20 UTCGHSA enrichment
  9. 2026-08-28 23:58 UTCEG score recompute
  10. 2026-08-28 23:57 UTCGHSA enrichment
  11. 2026-08-28 21:42 UTCEPSS rescore
  12. 2026-08-28 17:01 UTCGHSA enrichment
  13. 2026-08-28 12:38 UTCGHSA enrichment
  14. 2026-08-28 08:15 UTCGHSA enrichment
  15. 2026-08-28 03:56 UTCGHSA enrichment
  16. 2026-08-27 23:36 UTCGHSA enrichment
  17. 2026-08-27 19:15 UTCGHSA enrichment
  18. 2026-08-27 14:57 UTCEG score recompute
  19. 2026-08-27 14:57 UTCGHSA enrichment
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-27 10:37 UTCEG score recompute
  22. 2026-08-27 10:37 UTCGHSA enrichment
  23. 2026-08-27 06:19 UTCEG score recompute 9.80
  24. 2026-08-27 06:11 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  25. 2026-08-26 15:43 UTCNVD update
Show 2 more
  1. 2026-08-26 14:42 UTCEG score recompute
  2. 2026-08-26 14:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80558?
CVE-2026-80558 is a critical vulnerability published on August 26, 2026. In the Linux kernel, the following vulnerability has been resolved: libceph: Avoid using invalid osd indices from primary_temp A corrupted osdmap received from a Ceph monitor or OSD may contain osd indices in its pgtemp, primarytemp, pgupmap, and pgupmap_items parts that don't exist, i.e., that are…
When was CVE-2026-80558 disclosed?
CVE-2026-80558 was first published in the National Vulnerability Database on August 26, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80558 actively exploited?
CVE-2026-80558 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 58.0% of all scored CVEs.
What is the CVSS score of CVE-2026-80558?
CVE-2026-80558 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-80558?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80558, 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-80558

Explore →

Is Your Infrastructure Affected by CVE-2026-80558?

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