vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2026-98195

wifi: iwlegacy: fix broadcast stations deallocation

N/A
Published: October 6, 2026 at 08:44 AM UTC
Updated: October 19, 2026 at 10:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: iwlegacy: fix broadcast stations deallocation On the error path of __il4965_up(), il_dealloc_bcast_stations() clears only IL_STA_UCODE_ACTIVE, leaving IL_STA_BCAST set. This causes the same broadcast stations to be deallocated again by __il4965_down(). This can occur when RF_KILL is toggled during driver startup. To fix clear the entire 'used' field, since we will not do any other operations on the station.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel· Linux
90%
4.7c2fd34469d1623111e3c3db65cde533f3bddc26e
Vendor states this is fixed in 4.7 (unaffected)
Vendor states this is fixed in 5.10.* (unaffected)
Vendor states this is fixed in 5.10.271 (unaffected)
Vendor states this is fixed in 5.15.* (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Vendor states this is fixed in 6.1.* (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.* (unaffected)
Vendor states this is fixed in 6.12.112 (unaffected)
Vendor states this is fixed in 6.18.* (unaffected)
Vendor states this is fixed in 6.18.54 (unaffected)
Vendor states this is fixed in 6.6.* (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2.* (unaffected)
Vendor states this is fixed in 7.2.8 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (8)

Source: cverecord
https://git.kernel.org/stable/c/275d474a4b4bd4e73b18b1452f12e78806a8843a
Source: cverecord
https://git.kernel.org/stable/c/526fdd45548e22eee50ee1062abd88269d9f32e0
Source: cverecord
https://git.kernel.org/stable/c/c9a116d691364cd7f59d8329b395adcaf826d5c6
Source: cverecord
https://git.kernel.org/stable/c/85d847ff71fe736cbc15ada321256818e630e205
Source: cverecord
https://git.kernel.org/stable/c/1d84c2a3de449aceb94ed79eaefecdf1bedb6468
Source: cverecord
https://git.kernel.org/stable/c/55d34422c0d91436983028fd3c1546a1c2bee55f
Source: cverecord
https://git.kernel.org/stable/c/a9176fe666af1730cab92350f9c8cf67ebf14439
Source: cverecord
https://git.kernel.org/stable/c/b5526b780f8b297a76030410b96ba29153afb98f

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card