Answer in brief
CVE-2026-98341 records a Unknown severity vulnerability in wifi: cfg80211: don't free driver-owned scan requests. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4a58e7c38443154fce1b47910e1a9184f65c5d72 <e8c75736cfd0c6c87562cda2312e3fe5e2227955 || >=4a58e7c38443154fce1b47910e1a9184f65c5d72 <cf6da29d17994865f73ca70976495ea856909c63 || >=4a58e7c38443154fce1b47910e1a9184f65c5d72 <dab68a74e90b8e07f08ed9deaa5884857a3cfe89 | e8c75736cfd0c6c87562cda2312e3fe5e2227955, cf6da29d17994865f73ca70976495ea856909c63, dab68a74e90b8e07f08ed9deaa5884857a3cfe89 |
| Linux/Linuxgeneric | 3.14 | Not reported |
Published upstream
Oct 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 6, 2026
In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: don't free driver-owned scan requests When an interface goes down while a scan is running, cfg80211 completes the scan towards userspace and frees the scan request. However, the driver can be convinced that it owns the request, since the cancellation is (intended to be) asynchronous. The WARN_ON() in the netdev notifier was meant to catch this, but it's not actually avoidable, so it triggers and we get a UAF in scan_done(). There doesn't seem to be a great way around it, so just track that the driver is still convinced it owns the request, and then just free it on completion if it was already cancelled. Also remove the warnings since they can trigger in the intended architecture.
Quoted source text, attributed separately from HOL analysis.