CVE-2026-72217

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: Bound-check xdr_buf_to_bvec() stores before writing

xdr_buf_to_bvec() writes a bio_vec into the caller's array before testing whether that slot is in range, and the head branch performs the store with no check at all. When the caller's budget is exactly used up, the next store lands one element past the end of the array. The overflow label returns count - 1, which masks the surplus store but cannot undo it.

rq_bvec, the array passed by nfsd_vfs_write(), is allocated to exactly rq_maxpages entries with no slack. The OOB store can land in adjacent slab memory; the bv_len and bv_offset fields written there are derived from client-supplied RPC payload sizes.

Move the in-range check ahead of the store in the head, page-loop, and tail branches. With the check at the top of each sequence, count is incremented only after a successful store, so the overflow label can return count directly.

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: Bound-check xdr_buf_to_bvec() stores before writing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98414b42530af65cb984ffc12685096a3b5e179a
generic

SUNRPC: Bound-check xdr_buf_to_bvec() stores before writing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/69e18135e2a004a79505451dbef07314ea16e1eb
generic

SUNRPC: Bound-check xdr_buf_to_bvec() stores before writing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6029e711a818bf34d6c4b90cafee24f3afffa110
generic

SUNRPC: Bound-check xdr_buf_to_bvec() stores before writing - kernel/git/stable/linux.git - Linux kernel stable tree

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

SUNRPC: Bound-check xdr_buf_to_bvec() stores before writing - kernel/git/stable/linux.git - Linux kernel stable tree

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

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

Frequently asked(5)

What is CVE-2026-72217?
CVE-2026-72217 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Bound-check xdrbufto_bvec() stores before writing xdrbuftobvec() writes a biovec into the caller's array before testing whether that slot is in range, and the head branch performs the store with no check at all. When the…
When was CVE-2026-72217 disclosed?
CVE-2026-72217 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-72217 actively exploited?
CVE-2026-72217 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.7% of all scored CVEs.
What is the CVSS score of CVE-2026-72217?
CVE-2026-72217 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-72217?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72217, 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-72217

Explore →

Is Your Infrastructure Affected by CVE-2026-72217?

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