CVE-2026-53103

What the bug is

roc_abort_sync() can deadlock with roc_work(). roc_work() holds dev->mt76.mutex, while cancel_work_sync() waits for roc_work() to finish. If the caller already owns the same mutex, both sides block and no progress is possible. This deadlock can occur during station removal when mt76_sta_state() -> mt76_sta_remove() -> mt7925_mac_sta_remove_link() -> mt7925_mac_link_sta_remove() -> mt7925_roc_abort_sync() invokes cancel_work_sync() while roc_work() is still running and holding dev->mt76.mutex. This avoids the mutex deadlock and preserves exactly-once work ownership.

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/mt7925/main.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

mt7925_common

Check it on the machine

grep -wE 'CONFIG_MT76_CORE|CONFIG_MT7925_COMMON|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 mt7925_common

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. The build rule could not be established for 1 release, so nothing is claimed about those.

• bookworm?
• trixie, forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64, s390x/s390x

?

not established - no Makefile entry for the affected file

M

a module where it is built at all; some flavours do not build it

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_MT76_CORE, CONFIG_MT7925_COMMON, 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-06-24 (4 months ago)source

CVSS

no vector published, unrated

Attack vector

not published

EPSS

0.12%, higher than 1.9% 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.12	6.18.33	153bcba36c87
6.12	7.0.10	2d8e0053bca2
6.12	7.1	dd08ca3f092f
6.11.2	0	0