CVE-2026-98186

What the bug is

mwifiex_search_oui_in_ie() reads a pairwise-cipher (PTK) count from a beacon/probe-response RSN or WPA information element and then walks that many 4-byte OUIs, comparing each with memcmp(). The count comes straight from the (attacker-supplied) IE and is never checked against the element's own length, and the callers admit the element on element_id alone (has_ieee_hdr() / has_vendor_hdr(), no length check). A crafted RSN/WPA IE with a large pairwise count therefore makes the walk read up to 255 * 4 bytes past the element -- an out-of-bounds read of the kmemdup()'d beacon buffer, reachable from any AP whose beacon/probe response is processed during scan-result parsing. Pass the number of IE bytes available at the OUI list and bound the walk to the element. Keep the length signed and reject a negative value before any unsigned arithmetic, so a small or zero IE length cannot underflow to a large size_t and defeat the bound. Found by 0sec automated security-research tooling (https://0sec.ai).

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/marvell/mwifiex/scan.c

What this is

MARVELL MWIFIEX WIRELESS DRIVERMAINTAINERS section matched on drivers/net/wireless/marvell/mwifiex/ · linux-wireless@vger.kernel.org · Odd Fixes

Kernel module

mwifiex

Check it on the machine

grep -wE 'CONFIG_MWIFIEX|CONFIG_WLAN|CONFIG_WLAN_VENDOR_MARVELL' /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 mwifiex

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, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp
• trixieMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armel/rpi, riscv64/riscv64, s390x/s390x
• forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64, loong64/loong64, riscv64/riscv64, s390x/s390x

M

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

Build switches

CONFIG_MWIFIEX, CONFIG_WLAN, CONFIG_WLAN_VENDOR_MARVELL

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.0	5.10.271	77e642af7f2f
3.0	5.15.222	982b8fcdbb28
3.0	6.1.189	58767b41f872
3.0	6.6.158	2402c9e2644b
3.0	6.12.112	54a9cc5bd70b
3.0	6.18.54	8bbef2b1ebfb
3.0	7.2.8	46cda9d42f0d
3.0	7.3	e667aee1c192

Debian advisories