Look up another CVE · open CVE-2026-80617 in the interactive tracker
CVE-2026-80617
net: airoha: fix foe_check_time allocation size
Published 2026-08-28 (2 months ago) by the Linux kernel CNA. Subsystem drivers/net. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-80617 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
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | not affected | 6.12.113-1 | Nothing to do. trixie never shipped the vulnerable code. |
| Debian 14forky | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.5-1 | Update 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
foe_check_time is declared as u16 pointer but was allocated with only ppe_num_entries bytes instead of ppe_num_entries * sizeof(u16). When airoha_ppe_foe_verify_entry() is called with hash >= ppe_num_entries/2, it writes beyond the allocated buffer, causing heap buffer overflow and potential kernel crash.
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.
drivers/net/ethernet/airoha/airoha_ppe.c
- What this is
- AIROHA ETHERNET DRIVERMAINTAINERS section matched on drivers/net/ethernet/airoha/ · linux-arm-kernel@lists.infradead.org · Maintained
Check it on the machine
grep -wE 'CONFIG_ETHERNET|CONFIG_NET_AIROHA|CONFIG_NET_VENDOR_AIROHA' /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.
Show whether Debian builds this, per release
Debian does not build this code in 2 releases. The build rule could not be established for 2 releases, so nothing is claimed about those.
- bookworm, trixie?
- forky, sidn
- ?
- not established - no Makefile entry for the affected file
- n
- not enabled on any flavour - this release does not build the code
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
- Build switches
- CONFIG_ETHERNET, CONFIG_NET_AIROHA, CONFIG_NET_VENDOR_AIROHA
- 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
- 9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- network (AV:N)source
- EPSS
- 0.70%, higher than 52.3% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/net
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.18.33 | 6.18.40 | 112b5eff24e0 |
| 6.19 | 7.1.5 | 9f7cd1e26d2f |
| 6.19 | 7.2 | 5c121ee63568 |
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:NAttack vector, network
- The overflow is reached from netdev RX when hardware PPE reports HIT_UNBIND_RATE_REACHED; on Airoha EN7581/AN7583 CPE/router SoCs this path is driven by remotely sourced Ethernet WAN/LAN or WiFi traffic without local syscall access.
- AC:LAttack complexity, low
- An attacker controls packet 5-tuples and send rate to populate FOE entries and force CPU-reason 0x0f; roughly half of valid hash indices (hash >= ppe_num_entries/2) deterministically hit the undersized buffer, with only a 100ms per-hash software throttle.
- PR:NPrivileges required, none
- Exploitation requires only the ability to send network packets to or through the device's registered interfaces; no local account, capability, namespace admin rights, or authentication on the RX/offload path.
- UI:NUser interaction, none
- No cooperative victim action is needed beyond normal always-on routing/bridging of attacker-supplied packets through the Airoha Ethernet or mt76 WiFi RX handlers.
- S:UScope, unchanged
- Impact is confined to kernel heap memory corruption and privilege escalation within the host running the Airoha driver; it does not cross a VM, hypervisor, or IOMMU security boundary.
- C:HConfidentiality impact, high
- airoha_ppe_check_skb() performs an out-of-bounds read of ppe->foe_check_time[hash] before writing a u16 timestamp, and the adjacent heap overflow can expose or corrupt neighboring kernel objects.
- I:HIntegrity impact, high
- The same path writes a u16 beyond the allocated foe_check_time buffer, giving a kernel heap out-of-bounds write that can be leveraged for further memory corruption or control-flow manipulation.
- A:HAvailability impact, high
- The fix commit explicitly warns of heap buffer overflow and potential kernel crash; corrupted adjacent heap metadata or pointers from the OOB access can trigger oops, panic, or loss of network availability.