Look up another CVE · open CVE-2026-80943 in the interactive tracker
CVE-2026-80943
wifi: rtlwifi: rtl8192du: check QoS TID before indexing tids
Published 2026-09-11 (37 days 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-80943 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 | fixedDSA-6528-1 · 2026-09-29 · text | 6.12.111-1 | Update the kernel and reboot. DSA-6528-1 shipped the fix on 2026-09-29, in 6.12.111-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4817-1 · 2026-10-04 · text | 6.12.111-1~deb12u1 | Update the kernel and reboot. DLA-4817-1 shipped the fix on 2026-10-04, in 6.12.111-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
rtl92du_tx_fill_desc() uses ieee80211_get_tid() to read the QoS TID from the 802.11 header and then uses it as an index into sta_entry->tids[]. ieee80211_get_tid() returns the low 4-bit QoS TID value, so the result can be in the range 0..15. rtlwifi only allocates MAX_TID_COUNT entries for sta_entry->tids[], and MAX_TID_COUNT is 9. A QoS TID greater than 8 therefore indexes past the aggregation state array. Keep the default RTL_AGG_STOP state for out-of-range TIDs, matching rtl92cu_tx_fill_desc(). This issue was detected by our static analysis tool and confirmed by manual audit. UBSAN validation for the same bug pattern reports an array-index-out-of-bounds access with index 10 for type 'rtl_tid_data [9]'.
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/wireless/realtek/rtlwifi/rtl8192du/trx.c
- What this is
- REALTEK WIRELESS DRIVER (rtlwifi family)MAINTAINERS section matched on drivers/net/wireless/realtek/rtlwifi/ · linux-wireless@vger.kernel.org · Maintained
Check it on the machine
grep -wE 'CONFIG_RTL8192DU|CONFIG_RTLWIFI|CONFIG_WLAN|CONFIG_WLAN_VENDOR_REALTEK' /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 4 releases. The build rule could not be established for 1 release, so nothing is claimed about those.
- bookworm?
- trixie, forky, sid, bookworm · linux-6.12n
- ?
- 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_RTL8192DU, CONFIG_RTLWIFI, CONFIG_WLAN, CONFIG_WLAN_VENDOR_REALTEK
- 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-09-11 (37 days ago)source
- CVSS
- 7.6 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:Hsource recompute it - Attack vector
- adjacent network (AV:A)source
- EPSS
- 0.24%, higher than 14.5% 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.11 | 6.12.109 | 6e327f14e1c4 |
| 6.11 | 6.18.50 | 0c0b374e12d5 |
| 6.11 | 7.2.4 | 42785f7e8d31 |
| 6.11 | 7.3 | ed4f05d9f2f4 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4817-1 | 2026-10-04 | bookworm 6.12.111-1~deb12u1 | tracker |
| DSA-6528-1 | 2026-09-29 | trixie 6.12.111-1 | tracker |
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
- An adjacent Wi-Fi peer can trigger automatic open-mesh peering responses; ieee80211_get_tid() treats the self-protected action category 15 as a QoS TID, so rtl92du_tx_fill_desc() is reached over the wireless link.
- AC:LAttack complexity, low
- A valid peering-open frame deterministically allocates an authorized station and transmits a category-15 action frame into the vulnerable TX descriptor path; no race or other condition outside the attacker's control is required.
- PR:NPrivileges required, none
- Open 802.11s mesh accepts self-protected peering frames from unknown peers and automatically inserts an authorized station, so no credentials or local capabilities are required.
- UI:NUser interaction, none
- Once the rtl8192du interface is operating as a mesh point, mac80211 processes the attacker's frame and transmits the peering response without further victim action.
- S:UScope, unchanged
- The out-of-bounds access and any resulting crash remain in the host kernel and wireless device security authority, without crossing a VM, IOMMU, or sandbox boundary.
- C:LConfidentiality impact, low
- The bug reads one agg_state byte at a TID-selected offset; TIDs 9-15 index past tids[9] into adjacent heap, yielding only a tightly bounded heap-state oracle rather than arbitrary disclosure.
- I:LIntegrity impact, low
- The access does not overwrite kernel memory or provide an arbitrary-write primitive; the fetched byte can only influence AMPDU/RTS TX descriptor fields, giving limited transmission integrity impact.
- A:HAvailability impact, high
- UBSAN trap or panic-on-warning kernels can oops or panic on the deterministic bounds violation, and an adjacent peer can retrigger it after recovery.