CVE-2026-68159

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 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: 0.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

libceph: bound pg_{temp,upmap,upmap_items} length to CEPH_PG_MAX_SIZE

__decode_pg_temp() decodes an user-controlled length but only rejects values large enough to overflow the allocation; it does not bound it to CEPH_PG_MAX_SIZE. The helper backs both pg_temp and pg_upmap decoding, and apply_upmap()/get_temp_osds() later copy the decoded list into the fixed-size on-stack array struct ceph_osds.osds[CEPH_PG_MAX_SIZE]. A monitor that sends an OSDMap with a pg_temp/pg_upmap entry longer than 32 thus causes a stack out-of-bounds write.

An OSD set for a single PG can never exceed CEPH_PG_MAX_SIZE, so reject longer entries at decode time. The bound is well below the old overflow threshold, so it also covers the allocation-size overflow the previous check guarded against.

BUG: KASAN: stack-out-of-bounds in ceph_pg_to_up_acting_osds Write of size 4 ... by task exploit kasan_report (mm/kasan/report.c:595) ceph_pg_to_up_acting_osds (net/ceph/osdmap.c:2617 net/ceph/osdmap.c:2833) calc_target (net/ceph/osd_client.c:1638) __submit_request (net/ceph/osd_client.c:2394) ceph_osdc_start_request (net/ceph/osd_client.c:2490) ceph_osdc_call (net/ceph/osd_client.c:5164) rbd_dev_image_probe (drivers/block/rbd.c:6899) do_rbd_add (drivers/block/rbd.c:7138) ... kernel BUG at net/ceph/osdmap.c:2670!

[ idryomov: do the same in __decode_pg_upmap_items() ]

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 10, 2026

Last Modified

August 23, 2026

Advisory Details (8)

Auto-updated Oct 4, 2026
Patch available.
generic

libceph: bound pg_{temp,upmap,upmap_items} length to CEPH_PG_MAX_SIZE - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: bound pg_{temp,upmap,upmap_items} length to CEPH_PG_MAX_SIZE - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: bound pg_{temp,upmap,upmap_items} length to CEPH_PG_MAX_SIZE - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: bound pg_{temp,upmap,upmap_items} length to CEPH_PG_MAX_SIZE - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9f00f9cf2be293efe899db67dc5272e3a9c62717
generic

libceph: bound pg_{temp,upmap,upmap_items} length to CEPH_PG_MAX_SIZE - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/66eec4af1e080b695229c9a20635648a6d12fedf
generic

libceph: bound pg_{temp,upmap,upmap_items} length to CEPH_PG_MAX_SIZE - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/590b07ceea138d49c9b64f65d263aa902d3b4730
generic

libceph: bound pg_{temp,upmap,upmap_items} length to CEPH_PG_MAX_SIZE - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: bound pg_{temp,upmap,upmap_items} length to CEPH_PG_MAX_SIZE - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/42bc06c67d94d5f2a6b33294b0c4b07d8a47c515

Vendor Advisories for CVE-2026-68159(6)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-10-05ubuntu
redhatkernel-rt-0:4.18.0-553.169.1.rt7.510.el8_102026-09-28redhat
redhatkernel-0:4.18.0-553.169.1.el8_102026-09-28redhat
redhatkernel-0:6.12.0-211.58.1.el10_22026-09-23redhat
redhatkernel-0:5.14.0-687.49.1.el9_82026-09-17redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)
  • every version up to 6.1.187-1: fixed in 6.1.187-1
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1
  • every version up to 6.12.107-1~deb12u1: fixed in 6.12.107-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (33 versions)
  • every version up to 6.12.105-1: fixed in 6.12.105-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (161 versions)
  • every version up to 7.1.6-1: fixed in 7.1.6-1
—

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 40× in last 7d / 211× 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 387 total refreshes for this CVE.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-68159?
CVE-2026-68159 is a critical vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: libceph: bound pg{temp,upmap,upmapitems} length to CEPHPGMAX_SIZE decodepgtemp() decodes an user-controlled length but only rejects values large enough to overflow the allocation; it does not bound it to CEPHPGMAXSIZE. The helper…
When was CVE-2026-68159 disclosed?
CVE-2026-68159 was first published on August 10, 2026, with the most recent update on August 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68159 actively exploited?
CVE-2026-68159 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68159?
CVE-2026-68159 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68159?
A fix for CVE-2026-68159 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-68159 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-68159

Explore →

Is Your Infrastructure Affected by CVE-2026-68159?

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

Book a Demo →Browse All CVEs