CVE-2026-68156

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH 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: 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: refresh auth->authorizer_buf{,_len} after authorizer update

ceph_x_create_authorizer() caches au->buf->vec.iov_base and au->buf->vec.iov_len in struct ceph_auth_handshake. These cached values are then used by the messenger connect code when sending the authorizer.

ceph_x_update_authorizer() can rebuild the authorizer when a newer service ticket is available. If the rebuilt authorizer no longer fits in the existing buffer, ceph_x_build_authorizer() drops its reference to au->buf and allocates a new one. If this is the final reference, ceph_buffer_put() frees the old ceph_buffer and its vec.iov_base, but auth->authorizer_buf still points at that freed memory.

A subsequent msgr1 reconnect can therefore queue the stale pointer and trigger a KASAN slab-use-after-free in _copy_from_iter() while tcp_sendmsg() copies the authorizer.

Refresh auth->authorizer_buf and auth->authorizer_buf_len after a successful authorizer rebuild so the messenger sends the current buffer.

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
50%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 19, 2026

Advisory Details (8)

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

libceph: refresh auth->authorizer_buf{,_len} after authorizer update - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/79a273df64238a4ade8b709689a78589f755b8ef
generic

libceph: refresh auth->authorizer_buf{,_len} after authorizer update - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/75e82e8944ac1efe9fdb88bd2f14d9a031282bdf
generic

libceph: refresh auth->authorizer_buf{,_len} after authorizer update - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5ecfcd5c05866f185357700b81b461dae4f5ebb2
generic

libceph: refresh auth->authorizer_buf{,_len} after authorizer update - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/26f814187abceee90dbb29a02133adb4786fbb13
generic

libceph: refresh auth->authorizer_buf{,_len} after authorizer update - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2334e9997308305ee4fd508fdfe6086c4150ed60
generic

libceph: refresh auth->authorizer_buf{,_len} after authorizer update - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0060ec912292a550198d8d18ac95b433c92a7091
generic

libceph: refresh auth->authorizer_buf{,_len} after authorizer update - kernel/git/stable/linux.git - Linux kernel stable tree

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

libceph: refresh auth->authorizer_buf{,_len} after authorizer update - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/937d61f86d377a3aa578adae7a3dfcecdddf9d89

Vendor Advisories for CVE-2026-68156(2)

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 58× in last 7d / 72× 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-21 04:16 UTCVendor advisory
  2. 2026-08-21 04:16 UTCGHSA enrichment
  3. 2026-08-20 23:54 UTCEG score recompute
  4. 2026-08-20 23:54 UTCGHSA enrichment
  5. 2026-08-20 22:56 UTCEPSS rescore
  6. 2026-08-20 19:33 UTCGHSA enrichment
  7. 2026-08-20 15:12 UTCGHSA enrichment
  8. 2026-08-20 10:51 UTCGHSA enrichment
  9. 2026-08-20 06:30 UTCGHSA enrichment
  10. 2026-08-20 02:09 UTCGHSA enrichment
  11. 2026-08-19 21:47 UTCGHSA enrichment
  12. 2026-08-19 17:25 UTCEG score recompute
  13. 2026-08-19 17:25 UTCGHSA enrichment
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-19 16:55 UTCEG score recompute
  16. 2026-08-19 16:55 UTCGHSA enrichment
  17. 2026-08-19 15:21 UTCGHSA enrichment
  18. 2026-08-19 10:49 UTCGHSA enrichment
  19. 2026-08-19 06:28 UTCGHSA enrichment
  20. 2026-08-19 02:07 UTCGHSA enrichment
  21. 2026-08-18 21:46 UTCGHSA enrichment
  22. 2026-08-18 17:25 UTCEG score recompute
  23. 2026-08-18 17:25 UTCGHSA enrichment
  24. 2026-08-18 13:48 UTCEPSS rescore
  25. 2026-08-18 12:58 UTCGHSA enrichment
Show 47 more
  1. 2026-08-18 08:33 UTCGHSA enrichment
  2. 2026-08-18 04:04 UTCGHSA enrichment
  3. 2026-08-17 23:43 UTCGHSA enrichment
  4. 2026-08-17 19:21 UTCGHSA enrichment
  5. 2026-08-17 14:23 UTCEG score recompute
  6. 2026-08-17 14:23 UTCGHSA enrichment
  7. 2026-08-17 13:47 UTCEPSS rescore
  8. 2026-08-17 10:01 UTCGHSA enrichment
  9. 2026-08-17 05:40 UTCEG score recompute
  10. 2026-08-17 05:40 UTCGHSA enrichment
  11. 2026-08-17 05:11 UTCEG score recompute
  12. 2026-08-17 05:11 UTCGHSA enrichment
  13. 2026-08-17 02:22 UTCGHSA enrichment
  14. 2026-08-16 22:01 UTCGHSA enrichment
  15. 2026-08-16 17:40 UTCEG score recompute
  16. 2026-08-16 17:40 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 13:19 UTCGHSA enrichment
  19. 2026-08-16 08:58 UTCGHSA enrichment
  20. 2026-08-16 04:37 UTCEG score recompute
  21. 2026-08-16 04:37 UTCGHSA enrichment
  22. 2026-08-16 00:16 UTCGHSA enrichment
  23. 2026-08-15 19:55 UTCGHSA enrichment
  24. 2026-08-15 15:34 UTCGHSA enrichment
  25. 2026-08-15 11:13 UTCGHSA enrichment
  26. 2026-08-15 06:52 UTCGHSA enrichment
  27. 2026-08-15 01:41 UTCEG score recompute
  28. 2026-08-15 01:41 UTCGHSA enrichment
  29. 2026-08-15 01:30 UTCEPSS rescore
  30. 2026-08-14 21:20 UTCGHSA enrichment
  31. 2026-08-14 16:54 UTCGHSA enrichment
  32. 2026-08-14 12:33 UTCGHSA enrichment
  33. 2026-08-14 08:12 UTCGHSA enrichment
  34. 2026-08-14 03:51 UTCEG score recompute
  35. 2026-08-14 03:51 UTCGHSA enrichment
  36. 2026-08-13 23:30 UTCEG score recompute
  37. 2026-08-13 23:30 UTCGHSA enrichment
  38. 2026-08-13 22:45 UTCEG score recompute▲ 9.80
  39. 2026-08-13 22:45 UTCGHSA enrichment
  40. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  41. 2026-08-13 22:00 UTCEPSS rescore
  42. 2026-08-13 08:06 UTCEG score recompute
  43. 2026-08-13 08:06 UTCGHSA enrichment
  44. 2026-08-12 13:51 UTCEPSS rescore
  45. 2026-08-10 13:24 UTCNVD update
  46. 2026-08-10 12:21 UTCEG score recompute
  47. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68156?
CVE-2026-68156 is a critical vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: libceph: refresh auth->authorizerbuf{,len} after authorizer update cephxcreateauthorizer() caches au->buf->vec.iovbase and au->buf->vec.iovlen in struct cephauth_handshake. These cached values are then used by the messenger connect…
When was CVE-2026-68156 disclosed?
CVE-2026-68156 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68156 actively exploited?
CVE-2026-68156 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 50.2% of all scored CVEs.
What is the CVSS score of CVE-2026-68156?
CVE-2026-68156 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-68156?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68156, 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-68156

Explore →

Is Your Infrastructure Affected by CVE-2026-68156?

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

Start Free Scan →Browse All CVEs