CVE-2026-97492

wifi: mac80211: don't call ieee80211_handle_reconfig_failure when not needed

N/A
Published: September 24, 2026 at 04:04 PM UTC
Updated: October 21, 2026 at 01:21 PM 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
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: don't call ieee80211_handle_reconfig_failure when not needed In case reconfiguration of NAN fails, we call ieee80211_handle_reconfig_failure, that marks all interfaces as not in the driver. Then, at the error path of the reconfig, cfg80211_shutdown_all_interfaces is called to destroy all the interfaces. If we have any other interface but the NAN one, for example a BSS station, then when its state (links, stations) will be removed, we won't tell the driver about this, because we will think that the interfaces are not in the driver, and then drivers might remain with dangling pointers to objects like stations and links (at least for iwlwifi this is the case). ieee80211_handle_reconfig_failure is meant to be called after we cleaned up the state in the driver, there is no reason to call it for NAN reconfiguration failure. Fix the code to just warn in such a case, as we do in other error paths in reconfig where it is too complicated to rewind.

Affected

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

167e33f4f68cc8e4e3bdaf6d43641176c51f2d794.9
Vendor states this is fixed in 026637b864b16dfae238e7e1accded820a3d7ae8 (fixed)
Vendor states this is fixed in 60b96e44489d6775fe9cd8df619c29e0dc285c49 (fixed)
Vendor states this is fixed in 6ef85dd9f8c62c9a465a32901d09475a114e67bd (fixed)
Vendor states this is fixed in 6fb64029457cdcd77be546daf4c7c7cf04891857 (fixed)
Vendor states this is fixed in 7a8a3ff2815501f78f494808355ddf37e08647d0 (fixed)
Vendor states this is fixed in f27a5bda84ff3b0fea3de7572ff48e518e66cf5d (fixed)
Vendor states this is fixed in 4.9 (unaffected)
Vendor states this is fixed in 5.10.271 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.160 (unaffected)
Vendor states this is fixed in 7.2 (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.

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.

Free plan, no card