CVE-2026-72213

HIGHPre-NVD 7.17.1
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: 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:

mm/hugetlb: fix hugetlb cgroup rsvd charge/uncharge mismatch

In alloc_hugetlb_folio(), a single h_cg pointer is used for both the rsvd and non-rsvd hugetlb cgroup charges. When map_chg is set, hugetlb_cgroup_charge_cgroup_rsvd() stores the charged cgroup in h_cg, but the immediately following hugetlb_cgroup_charge_cgroup() overwrites h_cg with the non-rsvd cgroup pointer.

As a result, hugetlb_cgroup_commit_charge_rsvd() stores the wrong (non-rsvd) cgroup pointer into the folio's rsvd slot.

When the folio is later freed, free_huge_folio() unconditionally calls both hugetlb_cgroup_uncharge_folio() and hugetlb_cgroup_uncharge_folio_rsvd(). The rsvd uncharge reads back the wrong cgroup from the folio and decrements a counter that was never charged for that cgroup, causing a page_counter underflow:

page_counter underflow: -512 nr_pages=512 WARNING: mm/page_counter.c:61 at page_counter_cancel

Fix this by introducing a separate h_cg_rsvd pointer exclusively for the rsvd charge path, keeping the rsvd and non-rsvd charges fully independent through their charge, commit, and error uncharge paths.

CVSS v3
7.1
EG Score
7.1(high)
EG Risk
37(Track)
EG Risk 37/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (4)

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

mm/hugetlb: fix hugetlb cgroup rsvd charge/uncharge mismatch - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm/hugetlb: fix hugetlb cgroup rsvd charge/uncharge mismatch - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm/hugetlb: fix hugetlb cgroup rsvd charge/uncharge mismatch - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1697d253f51cf5e3825a3423ff49e128a3502ab2
generic

mm/hugetlb: fix hugetlb cgroup rsvd charge/uncharge mismatch - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/15807d0ddde37407af72859426b654f3d1972b00

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

Frequently asked(5)

What is CVE-2026-72213?
CVE-2026-72213 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: fix hugetlb cgroup rsvd charge/uncharge mismatch In allochugetlbfolio(), a single h_cg pointer is used for both the rsvd and non-rsvd hugetlb cgroup charges. When map_chg is set, hugetlbcgroupchargecgrouprsvd() stores…
When was CVE-2026-72213 disclosed?
CVE-2026-72213 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-72213 actively exploited?
CVE-2026-72213 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.4% of all scored CVEs.
What is the CVSS score of CVE-2026-72213?
CVE-2026-72213 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-72213?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72213, 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-72213

Explore →

Is Your Infrastructure Affected by CVE-2026-72213?

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