CVE-2026-98190

What the bug is

wilc_wfi_p2p_rx() and mgmt_tx() start parsing a frame once ieee80211_is_public_action() returns true. That helper only verifies the frame is long enough for the action category field, that is offsetofend(struct ieee80211_mgmt, u.action.category), 25 bytes. Both functions then read the P2P public action header up to oui_subtype at offset 30 and pass "size - ie_offset" to cfg80211_find_vendor_ie(), where ie_offset is offsetof(struct ieee80211_mgmt, u) + sizeof(*d), i.e. 32. A public action frame of 25 to 31 bytes passes the check but is shorter than that 32 byte header, so oui_subtype can be read out of bounds, and because the length is unsigned, "size - ie_offset" underflows to a value close to 4 GiB. cfg80211_find_vendor_ie() takes an unsigned int length, so even the size_t subtraction in mgmt_tx() is truncated to the same value. It then walks far past the buffer searching for a vendor element until it reaches unmapped memory. In the receive path the frame arrives over the air and needs no association, so a nearby unauthenticated device can crash the host while it is in P2P listen. Reject frames shorter than the P2P public action header in both paths before dereferencing it.

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/microchip/wilc1000/cfg80211.c

What this is

MICROCHIP WILC1000 WIFI DRIVERMAINTAINERS section matched on drivers/net/wireless/microchip/ · linux-wireless@vger.kernel.org · Supported

Kernel module

none to look for. The file would have gone into wilc1000, and Debian does not compile it into that module, so finding wilc1000 in lsmod would say nothing about this CVE.

Check it on the machine

grep -wE 'CONFIG_WILC1000|CONFIG_WLAN|CONFIG_WLAN_VENDOR_MICROCHIP' /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 4 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, sidn

n

not enabled on any flavour - this release does not build the code

Build switches

CONFIG_WILC1000, CONFIG_WLAN, CONFIG_WLAN_VENDOR_MICROCHIP

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
5.7	5.10.271	e98ad9f4c59f
5.7	5.15.222	f0c46f8111a4
5.7	6.1.189	a5b827dad8a3
5.7	6.6.158	491df93b10d7
5.7	6.12.112	cc2ee642ebea
5.7	6.18.54	68b786691ce2
5.7	7.2.8	6fbe76eb2796
5.7	7.3	ba6cb7c0868a

Debian advisories