data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-90357 in the interactive tracker

CVE-2026-90357

wifi: mt76: mt7915: unlink TWT flow if the MCU rejects the agreement

8.8 EPSS 0.3% AV:A

Published 2026-09-17 (31 days 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-90357 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

ReleaseStatus VersionWhat this means
Debian 12bookwormfixedDLA-4841-1 · 2026-10-17 · text6.1.190-1Update the kernel and reboot. DLA-4841-1 shipped the fix on 2026-10-17, in 6.1.190-1. A running kernel keeps the old code until the machine restarts.
Debian 13trixiefixedDSA-6528-1 · 2026-09-29 · text6.12.111-1Update 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 14forkyfixed7.2.6-1Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.2.6-1Update 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.12fixedDLA-4817-1 · 2026-10-04 · text6.12.111-1~deb12u1Update 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

The flow is added to dev->twt_list before sending the agreement to the firmware, but the error path leaves it linked while flowid_mask is never set. The flow slot can then be reused and memset while still on the list, corrupting twt_list, and station removal leaves a dangling entry behind that mt7915_mac_twt_sched_list_add() later walks.

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/mediatek/mt76/mt7915/mac.c

What this is
MEDIATEK MT76 WIRELESS LAN DRIVERMAINTAINERS section matched on drivers/net/wireless/mediatek/mt76/ · linux-wireless@vger.kernel.org · Maintained
Kernel module
mt7915e

Check it on the machine

grep -wE 'CONFIG_MT76_CORE|CONFIG_MT7915E|CONFIG_WLAN|CONFIG_WLAN_VENDOR_MEDIATEK' /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 mt7915e

Prints 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, s390x/s390x
  • forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64, s390x/s390x
  • bookworm · linux-6.12Mnot 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_MT76_CORE, CONFIG_MT7915E, CONFIG_WLAN, CONFIG_WLAN_VENDOR_MEDIATEK
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-17 (31 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.34%, higher than 26.0% 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

IntroducedFixed inCommit
5.166.1.188c09d1b15ed2d
5.166.6.1571bd5c4ed2b90
5.166.12.110cabe239e95b4
5.166.18.526bce0f1280c9
5.167.2.6beaa42b87596
5.167.316a04441eab0

Debian advisories

AdvisoryDateShipped toDebian
DLA-4841-12026-10-17bookworm 6.1.190-1tracker
DLA-4817-12026-10-04bookworm 6.12.111-1~deb12u1tracker
DSA-6528-12026-09-29trixie 6.12.111-1tracker

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
WLAN_S1G_TWT_SETUP action frames carry the TWT element into ieee80211_rx_h_action → ieee80211_process_rx_twt_action → ieee80211_s1g_rx_twt_setup → drv_add_twt_setup → mt7915_mac_add_twt_setup; the triggering bytes arrive over 802.11 radio on the AP’s LAN segment, so the vector is Adjacent.
AC:LAttack complexity, low
After mt7915_mcu_twt_agrt_update(..., MCU_TWT_AGRT_ADD) fails, a second TWT setup from the same STA does memset/INIT_LIST_HEAD on the still-linked msta->twt.flow[] slot because flowid_mask was never set. The attacker induces that ADD failure (MCU timeout or mt76_dma_tx_queue_skb_raw queue-full) with their own traffic, then retries or deauths; not a victim-only race.
PR:NPrivileges required, none
ieee80211_process_rx_twt_action only requires rx->sta on an AP with twt_responder; WLAN_CATEGORY_S1G TWT frames are not robust management frames, so MFP does not gate them. No Linux account or capability is needed: associating as a client to an open or guest mt7915 AP is enough to send the TWT setup.
UI:NUser interaction, none
The attacker sends the TWT Setup action frame and the follow-up retry or deauth; ieee80211_iface_work → ieee80211_s1g_rx_twt_action runs with no local user step. An already-running AP with twt_responder is standing configuration, not victim interaction during the attack.
S:UScope, unchanged
mt7915_mac_add_twt_setup corrupts the host kernel’s dev->twt_list and the mt7915_twt_flow embedded in sta->drv_priv; impact stays inside that kernel security authority and does not cross a VM, IOMMU, or guest-to-host boundary.
C:HConfidentiality impact, high
On DISASSOC, mt7915_mac_twt_teardown_flow returns immediately when flowid_mask is unset, then sta_info_free kfree’s the sta while the node remains on twt_list. A later mt7915_mac_twt_sched_list_add walk reads the freed mt7915_twt_flow, a use-after-free of attacker-reallocatable sta slab.
I:HIntegrity impact, high
The retry path memset/INIT_LIST_HEAD of a still-linked flow, and list_add in mt7915_mac_twt_sched_list_add, write next/prev through corrupted or freed list nodes, yielding a kernel write primitive from list corruption and the DISASSOC use-after-free.
A:HAvailability impact, high
mt7915_mac_twt_sched_list_add walking the corrupted or dangling twt_list oopses on a freed mt7915_twt_flow or spins forever on a self-linked node after INIT_LIST_HEAD, hanging or panicking the AP kernel.