CVE-2026-72235 json
batman-adv: retrieve ethhdr after potential skb realloc on RX
published 2026-08-15 2 mo ago modified 2026-10-16 23 d ago also EUVD-2026-59134
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 28%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
batman-adv: retrieve ethhdr after potential skb realloc on RX
pskb_may_pull() in batadv_interface_rx() 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.
This was done correctly for the VLAN header but missed for the ethernet header which is later used for the TT and AP isolation handling.
Patch / fix
- Linux Linux 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5, 7.2
- linux Debian 12 6.1.180-1
- linux Debian 13 6.12.100-1
- linux Debian 14 7.1.5-1
debian advisories DEBIAN-CVE-2026-72235
- linux Ubuntu 22.04 LTS 5.15.0-198.208
- linux Ubuntu 24.04 LTS 6.8.0-147.147
- linux Ubuntu 26.04 LTS 7.0.0-38.38
- linux-aws Ubuntu 22.04 LTS 5.15.0-1117.124
- linux-aws Ubuntu 24.04 LTS 6.8.0-1067.70
- linux-aws Ubuntu 26.04 LTS 7.0.0-1014.14
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1118.128
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1071.79
ubuntu advisories UBUNTU-CVE-2026-72235
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/6e189f14d1ea28db212b9d70a02131a7ce518012 commit
- git.kernel.org/stable/c/a1820344b180cb55af748f102bc536b5c93164db commit
- git.kernel.org/stable/c/6abf73589bed3f27ee240c08108feb72bed0b9c6 commit
- git.kernel.org/stable/c/f19259395b44af67f3c274e34237c295b526b859 commit
- git.kernel.org/stable/c/2cefa5141cab8ec1e4b24cf585958b13f2e3049d commit
- git.kernel.org/stable/c/85a71a81854e0e191ad0e533eabb4eff54866feb commit
- git.kernel.org/stable/c/b031fc97e1993d29d6c3a0e86a99140528cf31e8 commit
- git.kernel.org/stable/c/035e1fed892d3d06002a73ff73668f618a514644 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-72235 updated cvss 5.5
kernel: batman-adv: retrieve ethhdr after potential skb realloc on RX
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 23 d ago
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/6e189f14d1ea28db212b9d70a02131a7ce518012
- git.kernel.org /stable/c/a1820344b180cb55af748f102bc536b5c93164db
- git.kernel.org /stable/c/6abf73589bed3f27ee240c08108feb72bed0b9c6
- git.kernel.org /stable/c/f19259395b44af67f3c274e34237c295b526b859
- git.kernel.org /stable/c/2cefa5141cab8ec1e4b24cf585958b13f2e3049d
- git.kernel.org /stable/c/85a71a81854e0e191ad0e533eabb4eff54866feb
- git.kernel.org /stable/c/b031fc97e1993d29d6c3a0e86a99140528cf31e8
- git.kernel.org /stable/c/035e1fed892d3d06002a73ff73668f618a514644
Sources
- CVE List CVE-2026-72235
- NVD CVE-2026-72235
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.