Look up another CVE · open CVE-2026-93799 in the interactive tracker
CVE-2026-93799
wifi: iwlwifi: mvm: validate sta_id in BA window status notif
Published 2026-09-24 (24 days ago) by the Linux kernel CNA. Subsystem drivers/net. Debian urgency: not yet assigned.
Debian does not build this code. The per-release build detail is under "Where it lives" below.
What to do, per Debian release
Debian's own status for CVE-2026-93799 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 | vulnerable | 6.1.190-1 | No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication. |
| 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
BA_WINDOW_STATUS_NOTIFICATION_ID extracts a 5-bit sta_id from the firmware notification and uses it to index fw_id_to_mac_id[] without bounds checking. Validate sta_id before array access to prevent out-of-bounds indexing.
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/intel/iwlwifi/mvm/rx.c
- What this is
- INTEL WIRELESS WIFI LINK (iwlwifi)MAINTAINERS section matched on drivers/net/wireless/intel/iwlwifi/ · linux-wireless@vger.kernel.org · Supported
- Kernel module
- none to look for. The file would have gone into iwlmvm, and Debian does not compile it into that module, so finding iwlmvm in lsmod would say nothing about this CVE.
Check it on the machine
grep -wE 'CONFIG_IWLMEI|CONFIG_IWLMVM|CONFIG_IWLWIFI|CONFIG_WLAN|CONFIG_WLAN_VENDOR_INTEL' /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 5 releases below, every kernel flavour Debian publishes has the switch off, so the vulnerable file is compiled into no kernel binary Debian ships.
- bookworm, trixie, forky, sid, bookworm · linux-6.12n
- n
- not enabled on any flavour - this release does not build the code
- Build switches
- CONFIG_IWLMEI, CONFIG_IWLMVM, CONFIG_IWLWIFI, CONFIG_WLAN, CONFIG_WLAN_VENDOR_INTEL
- 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-24 (24 days ago)source
- CVSS
- 8.8 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- adjacent network (AV:A)source
- EPSS
- 0.24%, higher than 14.2% 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 |
|---|---|---|
| 4.6 | 6.6.158 | f9938eb95e2d |
| 4.6 | 6.12.111 | bb08fbbbd556 |
| 4.6 | 6.18.53 | e35ae757c646 |
| 4.6 | 7.2 | 6aa77efaea9e |
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
- The bad 5-bit sta_id is in BA_WINDOW_STATUS_NOTIFICATION (cmd 0x13) DMA'd from the Intel WiFi NIC. iwl_pcie_rx_handle_rb → iwl_op_mode_rx → iwl_mvm_rx → iwl_mvm_rx_common dispatches that notif to iwl_mvm_window_status_notif, which reports received MPDUs in the BA window; that is WiFi radio range, not a routable IP protocol.
- AC:LAttack complexity, low
- iwl_mvm_window_status_notif uses notif->ra_tid's 5-bit sta_id with no race or extra kernel gate beyond VALID and mpdu_rx_count != 0. A nearby peer that sends aggregated 802.11 traffic causes firmware to emit this BA window notif; once sta_id >= num_stations the fw_id_to_mac_id[] OOB is deterministic.
- PR:NPrivileges required, none
- iwl_mvm_window_status_notif is an RX_HANDLER_SYNC handler with no capability, socket, or 802.11 authentication check; iwl_mvm_rx_common invokes it from NAPI as soon as cmd 0x13 arrives. A radio-range attacker needs no host account.
- UI:NUser interaction, none
- The BA_WINDOW_STATUS_NOTIFICATION is processed automatically in iwl_pcie_napi_poll / iwl_mvm_rx_common on an already-up Intel WiFi interface; the attacker does not need the victim to open a file, mount media, or click through a prompt.
- S:UScope, unchanged
- The OOB index and the later type-confused ieee80211_mark_rx_ba_filtered_frames() call stay inside iwlwifi/mac80211 kernel memory on the same host; they do not cross a VM, IOMMU, or sandbox boundary.
- C:HConfidentiality impact, high
- sta_id is 5 bits (0-31) but fw_id_to_mac_id[] has IWL_STATION_COUNT_MAX (16) entries, so sta_id 16-31 reads adjacent fw_id_to_link_sta[] pointers as ieee80211_sta*. ieee80211_mark_rx_ba_filtered_frames() then container_of()s that into sta_info and follows sta->sdata and tid_rx, a type confusion that can disclose kernel memory.
- I:HIntegrity impact, high
- The same confused sta_info is used to write tid_agg_rx->head_seq_num and reorder_buf_filtered and to release reorder-buffer frames into ieee80211_rx_handlers(), so the fw_id_to_link_sta versus ieee80211_sta type confusion is a kernel write / RX-injection primitive.
- A:HAvailability impact, high
- Treating an ieee80211_link_sta* as ieee80211_sta* makes container_of() in ieee80211_mark_rx_ba_filtered_frames() compute a bogus sta_info, and the immediate sta->sdata->local dereference in NAPI oopses or panics.