Look up another CVE · open CVE-2026-52983 in the interactive tracker
CVE-2026-52983
net: airoha: fix BQL imbalance in TX path
Published 2026-06-24 (4 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-52983 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 | vulnerable | 6.12.113-1 | No fix published anywhere yet, neither in Debian nor upstream for the series trixie tracks. Watch the Debian tracker page for this CVE. Advisories for trixie have historically landed a median of 11 days after publication. |
| Debian 14forky | fixed | 7.0.10-1 | Update the kernel and reboot. Fixed in 7.0.10-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.10-1 | Update the kernel and reboot. Fixed in 7.0.10-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
Fix a possible BQL imbalance in airoha_dev_xmit(), where inflight packets are accounted only for the AIROHA_NUM_TX_RING netdev TX queues. The queue index is computed as: qid = skb_get_queue_mapping(skb) % ARRAY_SIZE(qdma->q_tx) txq = netdev_get_tx_queue(dev, qid); However, airoha_qdma_tx_napi_poll() accounts completions across all netdev TX queues (num_tx_queues), leading to inconsistent BQL accounting. Also reset all netdev TX queues in the ndo_stop callback.
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_eth.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 3 releases. The build rule could not be established for 1 release, 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-06-24 (4 months ago)source
- CVSS
- 7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Hsource recompute it - Attack vector
- network (AV:N)source
- EPSS
- 0.61%, higher than 48.1% 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.13 | 6.18.33 | aaad53a55812 |
| 6.13 | 7.0.10 | ded2694247a5 |
| 6.13 | 7.1 | 2d9f5a118205 |
| 6.12.91 | 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 vulnerable path is the Airoha Ethernet transmit path, and in a reasonable router/gateway or server deployment remote unauthenticated traffic can be forwarded or elicit responses transmitted through the affected interface.
- AC:LAttack complexity, low
- Once HTB offload/extra TX queues are present, packets mapped to those queues deterministically create mismatched BQL accounting and the TX completion path reaches dql_completed(); no race or hard-to-win condition is required.
- PR:NPrivileges required, none
- The attacker does not need credentials to send or induce network traffic through the configured interface; CAP_NET_ADMIN is only needed to create the traffic-shaping setup and may already be present in the deployed system.
- UI:NUser interaction, none
- No victim interaction is required after the affected network interface and queue configuration are active.
- S:UScope, unchanged
- The impact remains within the Linux kernel/network device security authority and does not cross a VM, IOMMU, or other separate security boundary.
- C:NConfidentiality impact, none
- The bug is a BQL accounting mismatch that triggers a BUG_ON in dql_completed, not a memory disclosure or memory corruption primitive.
- I:NIntegrity impact, none
- The investigated path does not provide arbitrary write, data modification, or control-flow corruption; it fails through a kernel assertion.
- A:HAvailability impact, high
- The mismatched completion accounting can trigger a kernel BUG/oops in the TX completion path, causing a system crash or denial of service.