CVE-2026-98349 json
wifi: libipw: reject too-short beacon and probe responses
published last mo. modified 23d ago also EUVD-2026-93334
- cvss
- 7.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 16%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
wifi: libipw: reject too-short beacon and probe responses
libipw_process_probe_response() and the libipw_network_init() call it makes assume the frame contains the full 36-byte beacon and probe response prefix, but the ipw2100 and ipw2200 receive paths only establish that a management frame carries the generic 24-byte three-address header.
libipw_network_init() then computes the information element length as
stats->len - sizeof(*beacon)
stats->len is a u16 and sizeof() has type size_t, so the subtraction is evaluated as size_t and wraps instead of going negative. Truncating that to the u16 length parameter of libipw_parse_info_param() yields 65524 for a 24-byte beacon, and the parser then walks the receive buffer as if it held almost 64 KiB of information elements, reading past the allocation.
Reject the frame before any fixed field is touched.
Found by an AI-assisted review of length arithmetic in management frame parsers. Verified with a KUnit case under Generic KASAN on arm64 under QEMU; I do not have the hardware, so it is not tested on a real device.
Patch / fix
- Linux Linux 7.3
- linux Debian 12 6.1.190-1
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.8-1
- linux-6.12 Debian 12 6.12.113-1~deb12u1
debian advisories DEBIAN-CVE-2026-98349
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 24.04 LTS 6.8.0-149.149
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 24.04 LTS 6.8.0-1069.74
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1073.81
ubuntu advisories UBUNTU-CVE-2026-98349
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source Linux Micro 6.0 6.4.0-159998.55.1
- kernel-default Linux Micro 6.0 6.4.0-159998.55.1
- kernel-kvmsmall Linux Micro 6.0 6.4.0-159998.55.1
- kernel-default-base Linux Micro 6.0 6.4.0-159998.55.1.159998.21.42
- kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.90.1
- kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.90.1
- kernel-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.53.90.1
- kernel-source SLE Module for Development Tools 15 SP7, SLE Module for Basesystem 15 SP7 6.4.0-150700.53.90.1
suse advisories SUSE-SU-2026:24550-1SUSE-SU-2026:5091-1
- kernel-source openSUSE Tumbleweed 7.2.10-1.1
opensuse advisories openSUSE-SU-2026:12131-1
- kernel Azure Linux 3.0 6.6.158.1-1
azure linux advisories AZL-106302
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/cee6f141b3bebe62eb0363fd147acb52023935f0 commit
- git.kernel.org/stable/c/23afeb5d2bdfd34c8a0a661876291a4fa9978293 commit
- git.kernel.org/stable/c/89959ff00a978f3172726d3d5f861ee6f1aae26d commit
- git.kernel.org/stable/c/14ae269c1306053ddf1ccf37c4bd66e085a652d1 commit
- git.kernel.org/stable/c/ff756e6647722b7d225d882f7bdb186d8eee318e commit
- git.kernel.org/stable/c/2c87bbc00dc93149d1dc4f803ad92d92e4ef3758 commit
- git.kernel.org/stable/c/19959fb60228f6dccc40d55507f8b1a751c2dc89 commit
- git.kernel.org/stable/c/5ce5721e8cbe3e80db8f43851cc2a2a92485ef4b commit
Is CVE-2026-98349 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-98349 updated cvss 5.5
kernel: wifi: libipw: reject too-short beacon and probe responses
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9not affected: vulnerable code not present
+1 more productsfewer
Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/cee6f141b3bebe62eb0363fd147acb52023935f0
- git.kernel.org /stable/c/23afeb5d2bdfd34c8a0a661876291a4fa9978293
- git.kernel.org /stable/c/89959ff00a978f3172726d3d5f861ee6f1aae26d
- git.kernel.org /stable/c/14ae269c1306053ddf1ccf37c4bd66e085a652d1
- git.kernel.org /stable/c/ff756e6647722b7d225d882f7bdb186d8eee318e
- git.kernel.org /stable/c/2c87bbc00dc93149d1dc4f803ad92d92e4ef3758
- git.kernel.org /stable/c/19959fb60228f6dccc40d55507f8b1a751c2dc89
- git.kernel.org /stable/c/5ce5721e8cbe3e80db8f43851cc2a2a92485ef4b
Sources
- CVE List CVE-2026-98349
- NVD CVE-2026-98349
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.