CVE-2026-98196

What the bug is

brcms_free_timer() calls brcms_del_timer() which uses the non-synchronous cancel_delayed_work() to cancel the timer's underlying delayed work. If the work callback (_brcms_timer) is already running, cancel_delayed_work() returns false without waiting, and brcms_free_timer() proceeds to kfree(t) while the callback still accesses t through container_of(). Add an explicit cancel_delayed_work_sync() after brcms_del_timer() to guarantee that any in-flight callback has completed before the timer structure is freed.

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/broadcom/brcm80211/brcmsmac/mac80211_if.c

What this is

BROADCOM BRCM80211 IEEE802.11 WIRELESS DRIVERSMAINTAINERS section matched on drivers/net/wireless/broadcom/brcm80211/ · linux-wireless@vger.kernel.org · Supported

Kernel module

brcmsmac

Check it on the machine

grep -wE 'CONFIG_BRCMFMAC|CONFIG_BRCMSMAC|CONFIG_WLAN|CONFIG_WLAN_VENDOR_BROADCOM' /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 brcmsmac

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
• trixie, forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64, s390x/s390x

M

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

Build switches

CONFIG_BRCMFMAC, CONFIG_BRCMSMAC, CONFIG_WLAN, CONFIG_WLAN_VENDOR_BROADCOM

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-10-06 (13 days ago)source

CVSS

no vector published, unrated

Attack vector

not published

EPSS

0.18%, higher than 7.5% 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
3.2	5.10.271	10eeb0b29fd7
3.2	5.15.222	74acccc92885
3.2	6.1.189	050d2486e8ed
3.2	6.6.158	856dabd5f261
3.2	6.12.112	2a4841ff0b74
3.2	6.18.54	1edb3ddd261e
3.2	7.2.8	777cb6bba59e
3.2	7.3	1eeca1d5e092

Debian advisories