Look up another CVE · open CVE-2026-80609 in the interactive tracker
CVE-2026-80609
qede: fix out-of-bounds check for cqe->len_list[]
Published 2026-08-28 (2 months ago) by the Linux kernel CNA. Subsystem drivers/net. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-80609 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 | fixed | 6.1.180-1 | Update the kernel and reboot. Fixed in 6.1.180-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 6.12.100-1 | Update the kernel and reboot. Fixed in 6.12.100-1. A running kernel keeps the old code until the machine restarts. |
| 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
Move index check before element 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.
drivers/net/ethernet/qlogic/qede/qede_fp.c
- What this is
- QLOGIC QL4xxx ETHERNET DRIVERMAINTAINERS section matched on drivers/net/ethernet/qlogic/qede/ · netdev@vger.kernel.org · Orphan
- Kernel module
- qede
Check it on the machine
grep -wE 'CONFIG_ETHERNET|CONFIG_NET_VENDOR_QLOGIC|CONFIG_QEDE' /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 qedePrints 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.
- bookwormMnot built on amd64/cloud-amd64, arm64/cloud-arm64
- trixieMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armel/rpi
- 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_ETHERNET, CONFIG_NET_VENDOR_QLOGIC, CONFIG_QEDE
- 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.74%, higher than 53.6% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- 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 |
|---|---|---|
| 5.15.197 | 5.15.212 | 6d203bdd227f |
| 6.1.159 | 6.1.178 | bd3a6a083b40 |
| 6.6.118 | 6.6.145 | e30af53dca80 |
| 6.12.60 | 6.12.97 | 1aacefd074b5 |
| 6.18 | 6.18.40 | b17751a2ebc4 |
| 6.18 | 7.1.5 | 6d46ab395803 |
| 6.18 | 7.2 | f9ba47fce593 |
| 6.17.10 | 0 | 0 |
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 bug is in qede TPA completion handling on the NAPI RX fastpath; remote TCP traffic to a Marvell/QLogic FastLinQ NIC causes firmware to post TPA CQEs that are parsed in qede_poll()->qede_rx_int()->qede_rx_process_tpa_cqe()->qede_tpa_cont()/qede_tpa_end().
- AC:LAttack complexity, low
- An attacker can repeatedly send high-rate crafted TCP bursts to maximize TPA aggregation BD counts so all len_list[] slots are non-zero, deterministically hitting the misordered bounds check without races, special memory layout, or victim-specific state.
- PR:NPrivileges required, none
- Only the ability to send Ethernet/TCP packets to a listening host with a qede interface is required; RX and TPA CQE processing occur in softirq before any authentication, capability checks, or local account access.
- UI:NUser interaction, none
- No victim action is needed beyond normal network operation; packet reception, interrupt handling, and NAPI polling automatically process attacker-supplied frames and completion descriptors.
- S:UScope, unchanged
- The out-of-bounds read and resulting skb/RX-ring corruption stay within the host kernel security boundary and do not cross VM, container, IOMMU, or sandbox isolation by themselves.
- C:HConfidentiality impact, high
- The loop reads past len_list[] into adjacent completion-descriptor memory before the bound check, and the same malformed CQE drives qede_fill_frag_skb() with attacker-influenced lengths that can leak uninitialized RX-ring/page data up the network stack.
- I:HIntegrity impact, high
- Extra qede_fill_frag_skb() iterations advance frag_id without MAX_SKB_FRAGS limits and consume RX BDs using firmware-supplied lengths, enabling controllable skb shared-info and RX-ring corruption exploitable for arbitrary kernel writes.
- A:HAvailability impact, high
- Corrupted skb fragment metadata and desynchronized RX BD consumption reliably trigger kernel oops/panic or wedged RX processing in softirq, and the condition is remotely repeatable for sustained denial of service.