CVE-2026-72222

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-15. 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:

sunrpc: pin svc_xprt across the asynchronous TLS handshake callback

svc_tcp_handshake() stores the raw svc_xprt pointer in tls_handshake_args.ta_data and submits the request through tls_server_hello_x509(). The handshake core takes only sock_hold(req->hr_sk); nothing references the embedding struct svc_sock that svc_tcp_handshake_done() reaches via container_of().

Two close races leave the in-flight callback writing through a freed svc_sock. svc_sock_free() calls tls_handshake_cancel() and discards its return value: a false return means handshake_complete() has already set HANDSHAKE_F_REQ_COMPLETED but hp_done() may not have finished, yet svc_sock_free() proceeds to kfree(svsk). The cancel-loser fall-through inside svc_tcp_handshake() itself produces the same window: when wait_for_completion_interruptible_timeout() returns <= 0 (timeout or signal) and tls_handshake_cancel() returns false, the function does not drain, returns, and svc_handle_xprt() calls svc_xprt_received(), which clears XPT_BUSY and can drop the last reference. A concurrent close then runs svc_sock_free() while svc_tcp_handshake_done() is still updating xpt_flags and walking svsk->sk_handshake_done.

The corruption surfaces as set_bit/clear_bit RMW into the freed xpt_flags slab slot and as complete_all() walking and writing the freed wait_queue_head_t list embedded in sk_handshake_done -- a slab-corruption primitive, not a benign read. The path is reachable on any TLS-enabled NFS server whenever a connection close overlaps the tlshd downcall delivery window; the interruptible wait means signal delivery suffices, not just SVC_HANDSHAKE_TO expiry.

Take svc_xprt_get(xprt) immediately before tls_server_hello_x509() so the in-flight callback owns its own reference. Release it on the two edges where the callback is guaranteed not to fire -- submission failure from tls_server_hello_x509() and a successful tls_handshake_cancel() -- and at the tail of svc_tcp_handshake_done() after complete_all().

[cel: rewrote commit message to describe the actual change]

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

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (5)

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

sunrpc: pin svc_xprt across the asynchronous TLS handshake callback - kernel/git/stable/linux.git - Linux kernel stable tree

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

sunrpc: pin svc_xprt across the asynchronous TLS handshake callback - kernel/git/stable/linux.git - Linux kernel stable tree

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

sunrpc: pin svc_xprt across the asynchronous TLS handshake callback - kernel/git/stable/linux.git - Linux kernel stable tree

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

sunrpc: pin svc_xprt across the asynchronous TLS handshake callback - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2d4f97d13fff91e0bc539216be88b884b544d49f
generic

sunrpc: pin svc_xprt across the asynchronous TLS handshake callback - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/083e9c2ec7e8bb13b79c9fd7b337abdd758ecc5f

Vendor Advisories for CVE-2026-72222(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 51× in last 7d / 51× 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 07:08 UTCGHSA enrichment
  2. 2026-08-21 03:27 UTCGHSA enrichment
  3. 2026-08-20 23:47 UTCEG score recompute
  4. 2026-08-20 23:47 UTCGHSA enrichment
  5. 2026-08-20 22:56 UTCEPSS rescore
  6. 2026-08-20 20:07 UTCGHSA enrichment
  7. 2026-08-20 16:27 UTCGHSA enrichment
  8. 2026-08-20 12:47 UTCGHSA enrichment
  9. 2026-08-20 09:06 UTCGHSA enrichment
  10. 2026-08-20 05:26 UTCGHSA enrichment
  11. 2026-08-20 01:45 UTCGHSA enrichment
  12. 2026-08-19 22:04 UTCGHSA enrichment
  13. 2026-08-19 18:24 UTCEG score recompute
  14. 2026-08-19 18:24 UTCGHSA enrichment
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-19 13:54 UTCGHSA enrichment
  17. 2026-08-19 10:12 UTCGHSA enrichment
  18. 2026-08-19 06:29 UTCGHSA enrichment
  19. 2026-08-19 02:48 UTCGHSA enrichment
  20. 2026-08-18 23:06 UTCGHSA enrichment
  21. 2026-08-18 19:26 UTCGHSA enrichment
  22. 2026-08-18 15:46 UTCEG score recompute
  23. 2026-08-18 15:46 UTCGHSA enrichment
  24. 2026-08-18 13:49 UTCEPSS rescore
  25. 2026-08-18 13:49 UTCEPSS rescore
Show 26 more
  1. 2026-08-18 12:04 UTCGHSA enrichment
  2. 2026-08-18 08:18 UTCGHSA enrichment
  3. 2026-08-18 04:27 UTCGHSA enrichment
  4. 2026-08-18 00:46 UTCGHSA enrichment
  5. 2026-08-17 21:02 UTCGHSA enrichment
  6. 2026-08-17 17:21 UTCEG score recompute
  7. 2026-08-17 17:21 UTCGHSA enrichment
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-17 13:40 UTCGHSA enrichment
  10. 2026-08-17 10:00 UTCEG score recompute
  11. 2026-08-17 10:00 UTCGHSA enrichment
  12. 2026-08-17 06:20 UTCEG score recompute
  13. 2026-08-17 06:20 UTCGHSA enrichment
  14. 2026-08-17 05:59 UTCEG score recompute 9.80
  15. 2026-08-17 05:59 UTCGHSA enrichment
  16. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  17. 2026-08-17 05:31 UTCEG score recompute
  18. 2026-08-17 05:31 UTCGHSA enrichment
  19. 2026-08-17 05:25 UTCMITRE cvelistV5
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 02:15 UTCEPSS rescore
  23. 2026-08-15 06:40 UTCGHSA enrichment
  24. 2026-08-15 06:23 UTCNVD update
  25. 2026-08-15 06:09 UTCEG score recompute
  26. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72222?
CVE-2026-72222 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: sunrpc: pin svc_xprt across the asynchronous TLS handshake callback svctcphandshake() stores the raw svc_xprt pointer in tlshandshakeargs.ta_data and submits the request through tlsserverhello_x509(). The handshake core takes only…
When was CVE-2026-72222 disclosed?
CVE-2026-72222 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72222 actively exploited?
CVE-2026-72222 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 52.6% of all scored CVEs.
What is the CVSS score of CVE-2026-72222?
CVE-2026-72222 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-72222?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72222, 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-72222

Explore →

Is Your Infrastructure Affected by CVE-2026-72222?

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