CVE-2026-72220

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: harden rq_procinfo lifecycle to prevent double-free

The svc_release_rqst() function executes the callback inside rqstp->rq_procinfo->pc_release. However, if a worker thread begins processing a new request and encounters an early error path (e.g., unsupported protocol, short frame, or bad auth) before a valid rq_procinfo is installed, a stale release hook can be re-triggered against reused state from the previous RPC, resulting in a double-free or use-after-free vulnerability.

Harden the lifecycle of rq_procinfo by:

  • Ensuring svc_release_rqst() always clears rq_procinfo after the
optional pc_release() call, regardless of whether the hook exists.
  • Explicitly clearing rq_procinfo at request entry in svc_process()
before any early decode or drop paths.
  • Ensuring svc_process_bc() does the same at backchannel entry.

This guarantees that error flows will not encounter a non-NULL stale rq_procinfo pointer when there is nothing to release.

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

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (3)

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

sunrpc: harden rq_procinfo lifecycle to prevent double-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/66014ab165cb01bfef5836939412a8ef98d5d5ff
generic

sunrpc: harden rq_procinfo lifecycle to prevent double-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/31ba490c02d476a5e4f90b8845932ac9db8aa71b
generic

sunrpc: harden rq_procinfo lifecycle to prevent double-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/18d216788bef06332ff8901670ecf1ed8f6eb614

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

Frequently asked(5)

What is CVE-2026-72220?
CVE-2026-72220 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: sunrpc: harden rq_procinfo lifecycle to prevent double-free The svcreleaserqst() function executes the callback inside rqstp->rqprocinfo->pcrelease. However, if a worker thread begins processing a new request and encounters an…
When was CVE-2026-72220 disclosed?
CVE-2026-72220 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-72220 actively exploited?
CVE-2026-72220 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 54.4% of all scored CVEs.
What is the CVSS score of CVE-2026-72220?
CVE-2026-72220 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-72220?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72220, 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-72220

Explore →

Is Your Infrastructure Affected by CVE-2026-72220?

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

Start Free Scan →Browse All CVEs