data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-80599 in the interactive tracker

CVE-2026-80599

batman-adv: dat: ensure accessible eth_hdr proto field

8.1 EPSS 0.4% AV:A

Published 2026-08-28 (2 months ago) by the Linux kernel CNA. Subsystem net/batman-adv. Debian urgency: not yet assigned.

What to do, per Debian release

Debian's own status for CVE-2026-80599 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormfixed6.1.180-1Update the kernel and reboot. Fixed in 6.1.180-1. A running kernel keeps the old code until the machine restarts.
Debian 13trixiefixed6.12.100-1Update the kernel and reboot. Fixed in 6.12.100-1. A running kernel keeps the old code until the machine restarts.
Debian 14forkyfixed7.1.5-1Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.1.5-1Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

When batadv_get_vid() accesses the proto field of the ethernet header, it is not checking if the data itself is accessible. The caller is responsible for it. But in contrast to other call sites, batadv_dat_get_vid() and its caller didn't make sure this is true. This could have caused an out-of-bounds access.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

net/batman-adv/distributed-arp-table.c
net/batman-adv/main.c

What this is
BATMAN ADVANCEDMAINTAINERS section matched on net/batman-adv/ · b.a.t.m.a.n@lists.open-mesh.org · Maintained
Kernel module
batman_adv

Check it on the machine

grep -wE 'CONFIG_BATMAN_ADV|CONFIG_BATMAN_ADV_DAT' /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

lsmod | grep -w batman_adv

Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.

Show whether Debian builds this, per release

Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.

  • bookworm, trixie, forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64
M
a module where it is built at all; some flavours do not build it
Build switches
CONFIG_BATMAN_ADV, CONFIG_BATMAN_ADV_DAT
Reads as
all on means the file is compiled; any one off means it is not.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published
2026-08-28 (2 months ago)source
CVSS
8.1 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:Hsource recompute it
Attack vector
adjacent network (AV:A)source
EPSS
0.42%, higher than 34.7% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
not yet assignedsource
Subsystem
net/batman-adv

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
3.135.10.261da3677b5ed36
3.135.15.2126d3ea37074bb
3.136.1.1787913935d41f1
3.136.6.1453c62694c31f0
3.136.12.975836a050d02e
3.136.18.408f76277d0217
3.137.1.54407ff3af469
3.137.226560c4a03dc

Why the CNA scored it this way

Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source

AV:AAttack vector, adjacent network
Exploitation requires injecting crafted ETH_P_BATMAN frames on the victim's batman-adv hard interface via batadv_batman_skb_recv(); an attacker must be on the same L2 mesh segment (WiFi community mesh, industrial mesh, or shared Ethernet backbone), not arbitrary Internet routing.
AC:LAttack complexity, low
The attacker fully controls remote packet length and contents; sending a batman-adv unicast or broadcast frame with only the batman header (10 or 14 bytes) and no embedded Ethernet payload bypasses hdr_size-only pskb_may_pull checks and deterministically forces the h_proto read past skb->tail without races or rare configuration.
PR:NPrivileges required, none
No Linux account or capability on the victim is required; any unauthenticated mesh peer that can transmit ETH_P_BATMAN frames to an active batman-adv node with Distributed ARP Table enabled reaches batadv_dat_snoop_incoming_*() through the normal RX handler without local login or CAP_NET_ADMIN on the target.
UI:NUser interaction, none
The vulnerable path runs automatically in softirq when the mesh interface receives qualifying traffic; no victim mount, click, or administrative action is needed beyond batman-adv already running with DAT enabled (the default at mesh interface creation).
S:UScope, unchanged
Impact is an out-of-bounds kernel read during batman-adv packet processing on the receiving mesh node; it does not cross a VM, container, or IOMMU security boundary to affect a different authority's resources.
C:HConfidentiality impact, high
batadv_get_vid() reads ethhdr->h_proto (2 bytes at offset 12 within the embedded Ethernet header) without ensuring hdr_size+ETH_HLEN bytes are accessible, causing an out-of-bounds read of adjacent skb tailroom or slab memory beyond the packet buffer per kernel OOB-read guidance.
I:NIntegrity impact, none
This is an out-of-bounds read only with no memory write or corruption; subsequent batadv_arp_get_type() performs its own pskb_may_pull() before further parsing, and the DAT snoop path returns without modifying kernel structures beyond the illicit read.
A:HAvailability impact, high
Reading past skb->tail in NET_RX_SOFTIRQ can provoke a kernel oops or panic when the access crosses an unmapped page boundary, denying mesh and host connectivity; any out-of-bounds kernel access on the packet receive path is rated high availability impact.