CVE-2026-72233

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

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

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

batman-adv: bla: reacquire gw address after skb realloc

The pskb_may_pull() called by batadv_bla_is_backbone_gw() could reallocate the buffer behind the skb. Variables which were pointing to the old buffer need to be reassigned to avoid an use-after-free.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
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: bla: reacquire gw address after skb realloc - kernel/git/stable/linux.git - Linux kernel stable tree

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

batman-adv: bla: reacquire gw address after skb realloc - kernel/git/stable/linux.git - Linux kernel stable tree

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

batman-adv: bla: reacquire gw address after skb realloc - kernel/git/stable/linux.git - Linux kernel stable tree

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

batman-adv: bla: reacquire gw address after skb realloc - kernel/git/stable/linux.git - Linux kernel stable tree

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

batman-adv: bla: reacquire gw address after skb realloc - kernel/git/stable/linux.git - Linux kernel stable tree

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

batman-adv: bla: reacquire gw address after skb realloc - kernel/git/stable/linux.git - Linux kernel stable tree

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

batman-adv: bla: reacquire gw address after skb realloc - kernel/git/stable/linux.git - Linux kernel stable tree

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

batman-adv: bla: reacquire gw address after skb realloc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/41819c5467b6eb8ab4567f0ac98702ce9b6abbb1

Vendor Advisories for CVE-2026-72233(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-21 01:21 UTCEG score recompute
  2. 2026-08-21 01:21 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 14:06 UTCGHSA enrichment
  5. 2026-08-20 02:49 UTCEG score recompute
  6. 2026-08-20 02:49 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 15:34 UTCGHSA enrichment
  9. 2026-08-19 04:15 UTCGHSA enrichment
  10. 2026-08-18 17:00 UTCEG score recompute
  11. 2026-08-18 17:00 UTCGHSA enrichment
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 04:56 UTCGHSA enrichment
  15. 2026-08-17 17:40 UTCEG score recompute
  16. 2026-08-17 17:40 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 8.80
  21. 2026-08-17 05:59 UTCGHSA enrichment
  22. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 8.8 · 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-72233?
CVE-2026-72233 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: batman-adv: bla: reacquire gw address after skb realloc The pskbmaypull() called by batadvblaisbackbonegw() could reallocate the buffer behind the skb. Variables which were pointing to the old buffer need to be reassigned to avoid…
When was CVE-2026-72233 disclosed?
CVE-2026-72233 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-72233 actively exploited?
CVE-2026-72233 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 72.9% of all scored CVEs.
What is the CVSS score of CVE-2026-72233?
CVE-2026-72233 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-72233?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72233, 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-72233

Explore →

Is Your Infrastructure Affected by CVE-2026-72233?

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