CVE-2026-72231

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

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

batman-adv: tt: avoid request storms during pending request

batadv_send_tt_request() allocates a tt_req_node when none exists for the destination originator node. This should prevent that a multiple TT requests are send at the same time to an originator.

But if allocation of the send buffer failed, this request must be cleaned up again. But indicator for such a failure is "ret == false". But the actual implementation is checking for "ret == true".

The check must be inverted to not loose the information about the TT request directly after it was attempted to be sent out. This should avoid potential request storms.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
39(Track)
EG Risk 39/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
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
50%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (8)

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

batman-adv: tt: avoid request storms during pending request - kernel/git/stable/linux.git - Linux kernel stable tree

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

batman-adv: tt: avoid request storms during pending request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/716f434eb35869e130424331584a91fbb729b9bd
generic

batman-adv: tt: avoid request storms during pending request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6a65ac8a81e903bb4b555c1d13532f5cb0167a4a
generic

batman-adv: tt: avoid request storms during pending request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6055695ea40c64a47e00742c12c99b1a33b4daed
generic

batman-adv: tt: avoid request storms during pending request - kernel/git/stable/linux.git - Linux kernel stable tree

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

batman-adv: tt: avoid request storms during pending request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/27c7d40008231ae4140d35501b60087a9de2d2c3
generic

batman-adv: tt: avoid request storms during pending request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/21c44a6895f41df811d1c91d10eea194dda2b345
generic

batman-adv: tt: avoid request storms during pending request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/067e413eec2e63c2996909ef55214b3a0eda0be7

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

Frequently asked(5)

What is CVE-2026-72231?
CVE-2026-72231 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: batman-adv: tt: avoid request storms during pending request batadvsendttrequest() allocates a ttreq_node when none exists for the destination originator node. This should prevent that a multiple TT requests are send at the same…
When was CVE-2026-72231 disclosed?
CVE-2026-72231 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-72231 actively exploited?
CVE-2026-72231 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 50.1% of all scored CVEs.
What is the CVSS score of CVE-2026-72231?
CVE-2026-72231 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-72231?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72231, 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-72231

Explore →

Is Your Infrastructure Affected by CVE-2026-72231?

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

Start Free Scan →Browse All CVEs