Skip to main content
VulnerabilityPublished Updated

CVE-2026-97492: Linux kernel · wifi: mac80211: don't call ieee80211_handle_reconfig_failure when not needed

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in f27a5bda84ff3b0fea3de7572ff48e518e66cf5d : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:18 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in f27a5bda84ff3b0fea3de7572ff48e518e66cf5d, d2ea99884793c0a8d940073c3dddbb887590718f, 026637b864b16dfae238e7e1accded820a3d7ae8 +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 167e33f4f68cc8e4e3bdaf6d43641176c51f2d79, < f27a5bda84ff3b0fea3de7572ff48e518e66cf5d
Fixed in
  • f27a5bda84ff3b0fea3de7572ff48e518e66cf5d
LinuxLinuxAffected
  • ≥ 167e33f4f68cc8e4e3bdaf6d43641176c51f2d79, < d2ea99884793c0a8d940073c3dddbb887590718f
Fixed in
  • d2ea99884793c0a8d940073c3dddbb887590718f
LinuxLinuxAffected
  • ≥ 167e33f4f68cc8e4e3bdaf6d43641176c51f2d79, < 026637b864b16dfae238e7e1accded820a3d7ae8
Fixed in
  • 026637b864b16dfae238e7e1accded820a3d7ae8
LinuxLinuxAffected
  • ≥ 167e33f4f68cc8e4e3bdaf6d43641176c51f2d79, < 60b96e44489d6775fe9cd8df619c29e0dc285c49
Fixed in
  • 60b96e44489d6775fe9cd8df619c29e0dc285c49
LinuxLinuxAffected
  • ≥ 167e33f4f68cc8e4e3bdaf6d43641176c51f2d79, < 7a8a3ff2815501f78f494808355ddf37e08647d0
Fixed in
  • 7a8a3ff2815501f78f494808355ddf37e08647d0
LinuxLinuxAffected
  • ≥ 167e33f4f68cc8e4e3bdaf6d43641176c51f2d79, < 6fb64029457cdcd77be546daf4c7c7cf04891857
Fixed in
  • 6fb64029457cdcd77be546daf4c7c7cf04891857

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.

References

Community reviews

Loading reviews…