CVE-2026-72431

UNRATEDCVSS · not yet scoredTrending — 5 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: 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:

alloc_tag: fix use-after-free in /proc/allocinfo after module unload

allocinfo_start() only reinitializes the codetag iterator at position 0. For subsequent reads (position > 0), it reuses cached iterator state from the previous batch. allocinfo_stop() drops mod_lock between read batches, which allows module unload to complete and free the module memory that the cached iterator still references:

CPU0 (read) CPU1 (rmmod) ---- ---- allocinfo_start(pos=0) down_read(mod_lock) allocinfo_show() ... allocinfo_stop() up_read(mod_lock) codetag_unload_module() kfree(cmod) release_module_tags() ... free_mod_mem() allocinfo_start(pos=N) down_read(mod_lock) // reuses cached iter, skips re-init allocinfo_show() ct->filename <-- UAF

After free_mod_mem() frees the module's .rodata, allocinfo_show() dereferences ct->filename, ct->function which point there.

Save the iterator state in allocinfo_next() and resume from it in allocinfo_start() with codetag_next_ct(), which detects module removal via idr_find() returning NULL and skips to the next module.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

References (3)

Vendor Advisories for CVE-2026-72431(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 18× in last 7d / 18× 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 22:56 UTCEPSS rescore
  2. 2026-08-20 01:54 UTCGHSA enrichment
  3. 2026-08-19 17:04 UTCEPSS rescore
  4. 2026-08-18 13:49 UTCEPSS rescore
  5. 2026-08-18 13:49 UTCEPSS rescore
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-17 06:28 UTCGHSA enrichment
  8. 2026-08-17 06:22 UTCNVD update
  9. 2026-08-17 05:29 UTCEG score recompute
  10. 2026-08-17 05:29 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:33 UTCGHSA enrichment
  16. 2026-08-15 06:23 UTCNVD update
  17. 2026-08-15 06:04 UTCEG score recompute
  18. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-72431?
CVE-2026-72431 is a publicly disclosed vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: alloc_tag: fix use-after-free in /proc/allocinfo after module unload allocinfo_start() only reinitializes the codetag iterator at position 0. For subsequent reads (position > 0), it reuses cached iterator state from the previous…
When was CVE-2026-72431 disclosed?
CVE-2026-72431 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-72431 actively exploited?
CVE-2026-72431 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 90.1% of all scored CVEs.
How do I remediate CVE-2026-72431?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72431, 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-72431

Explore →

Is Your Infrastructure Affected by CVE-2026-72431?

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

Start Free Scan →Browse All CVEs