CVE-2026-98188

What the bug is

p54_convert_rev0() and p54_convert_rev1() read calibration curve data from the device-supplied EEPROM entry using channel and points-per-channel counts taken verbatim from that same entry, so an entry that declares more data than it carries drives an out-of-bounds read past the EEPROM buffer (verified with a KASAN reproducer of the conversion loop). The sibling converters p54_convert_output_limits() and p54_convert_db() already validate their counts against the entry length; this path was missed. Reject the entry when the counts do not fit in the entry data.

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/intersil/p54/eeprom.c

What this is

P54 WIRELESS DRIVERMAINTAINERS section matched on drivers/net/wireless/intersil/ · linux-wireless@vger.kernel.org · Maintained

Kernel module

p54common

Check it on the machine

grep -wE 'CONFIG_P54_COMMON|CONFIG_WLAN|CONFIG_WLAN_VENDOR_INTERSIL' /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 p54common

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_P54_COMMON, CONFIG_WLAN, CONFIG_WLAN_VENDOR_INTERSIL

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 6.7% 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
2.6.24	5.10.271	81084c967c18
2.6.24	5.15.222	41cdf14bf4b5
2.6.24	6.1.189	03d313e3dfb4
2.6.24	6.6.158	42f4b03971f9
2.6.24	6.12.112	4d767d6f8753
2.6.24	6.18.54	3bdcc4d61212
2.6.24	7.2.8	b0c906107150
2.6.24	7.3	ce858fa6b8a2

Debian advisories