CVE-2026-64090 json
batman-adv: tt: avoid empty VLAN responses
published 2026-07-19 3 mo ago modified 2026-08-11 2 mo ago also EUVD-2026-45775
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
batman-adv: tt: avoid empty VLAN responses
The commit 16116dac2339 ("batman-adv: prevent TT request storms by not sending inconsistent TT TLVLs") added checks to the local (direct) TT response code. But the response can also be done indirectly by another node using the global TT state. To avoid such inconsistency states reported in the original fix, also avoid sending empty VLANs for replies from the global TT state.
Patch / fix
- Linux Linux 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.93, 6.18.34, 7.0.11, 7.1
- linux Debian 12 6.1.176-1
- linux Debian 13 6.12.94-1
- linux Debian 14 7.0.12-1
debian advisories DEBIAN-CVE-2026-64090
- linux Ubuntu 22.04 LTS 5.15.0-198.208
- linux Ubuntu 24.04 LTS 6.8.0-146.146
- linux Ubuntu 26.04 LTS 7.0.0-28.28
- linux-aws Ubuntu 22.04 LTS 5.15.0-1117.124
- linux-aws Ubuntu 24.04 LTS 6.8.0-1066.69
- linux-aws Ubuntu 26.04 LTS 7.0.0-1009.9
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1118.128
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1070.78
ubuntu advisories UBUNTU-CVE-2026-64090
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/1f467d9a095211d3f77e8ff1bee90e73ffe01c64 commit
- git.kernel.org/stable/c/9a02c8fc963ddeecb5d8788be0740c1869fc54b7 commit
- git.kernel.org/stable/c/ea4f757641430bcc8322772e161453c4db5ecb64 commit
- git.kernel.org/stable/c/99f17d1cdb371cbd037975239b321f346d38f6d2 commit
- git.kernel.org/stable/c/cfb30645280a2131e46cbd1b9a38cfd3ff893f12 commit
- git.kernel.org/stable/c/b93ca6012712ecab2b551e120d7c95038d6a89e5 commit
- git.kernel.org/stable/c/ab26e346322648f5c39de017d9723c9256284fce commit
- git.kernel.org/stable/c/fa1bd704940b5bcbc32c0b28db9167405c8ee5e0 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-64090 updated
kernel: batman-adv: tt: avoid empty VLAN responses
-
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
Exploit prediction
0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/1f467d9a095211d3f77e8ff1bee90e73ffe01c64
patch
-
git.kernel.org
/stable/c/9a02c8fc963ddeecb5d8788be0740c1869fc54b7
patch
-
git.kernel.org
/stable/c/ea4f757641430bcc8322772e161453c4db5ecb64
patch
-
git.kernel.org
/stable/c/99f17d1cdb371cbd037975239b321f346d38f6d2
patch
-
git.kernel.org
/stable/c/cfb30645280a2131e46cbd1b9a38cfd3ff893f12
patch
-
git.kernel.org
/stable/c/b93ca6012712ecab2b551e120d7c95038d6a89e5
patch
-
git.kernel.org
/stable/c/ab26e346322648f5c39de017d9723c9256284fce
patch
-
git.kernel.org
/stable/c/fa1bd704940b5bcbc32c0b28db9167405c8ee5e0
patch
Sources
- CVE List CVE-2026-64090
- NVD CVE-2026-64090
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.