CVE-2026-90345

What the bug is

Some P2P action frame paths assume the P2P device vif is always available. That is not true when userspace sends non-P2P public action frames through the primary interface, or when action-frame abort runs after the P2P device vif has not been created. Fall back to the primary vif when aborting an action frame without a P2P device vif, and guard P2P device saved IE access before using it for peer channel search.

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/brcmfmac/p2p.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

brcmfmac

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 brcmfmac

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-09-17 (31 days ago)source

CVSS

no vector published, unrated

Attack vector

not published

EPSS

0.21%, higher than 10.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

Introduced	Fixed in	Commit
3.9	6.18.57	f334b26b884d
3.9	7.2.6	f26e1b169045
3.9	7.3	1b1edb9ebed4