CVE-2026-97492: wifi: mac80211: don't call ieee80211_handle_reconfig_failure when not needed
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 026637b864b16dfae238e7e1accded820a3d7ae8, 60b96e44489d6775fe9cd8df619c29e0dc285c49, 6ef85dd9f8c62c9a465a32901d09475a114e67bd; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1.
Low priority for now. Upgrade to Linux Linux 026637b864b16dfae238e7e1accded820a3d7ae8, 60b96e44489d6775fe9cd8df619c29e0dc285c49, 6ef85dd9f8c62c9a465a32901d09475a114e67bd; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 24, 2026
- Updated
- Oct 21, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.9affected
- 167e33f4f68cc8e4e3bdaf6d43641176c51f2d79 and later · before 026637b864b16dfae238e7e1accded820a3d7ae8affected · git
- 167e33f4f68cc8e4e3bdaf6d43641176c51f2d79 and later · before 6ef85dd9f8c62c9a465a32901d09475a114e67bdaffected · git
- 167e33f4f68cc8e4e3bdaf6d43641176c51f2d79 and later · before f27a5bda84ff3b0fea3de7572ff48e518e66cf5daffected · git
- 167e33f4f68cc8e4e3bdaf6d43641176c51f2d79 and later · before d2ea99884793c0a8d940073c3dddbb887590718faffected · git
- 167e33f4f68cc8e4e3bdaf6d43641176c51f2d79 and later · before 60b96e44489d6775fe9cd8df619c29e0dc285c49affected · git
- 167e33f4f68cc8e4e3bdaf6d43641176c51f2d79 and later · before 6fb64029457cdcd77be546daf4c7c7cf04891857affected · git
- 167e33f4f68cc8e4e3bdaf6d43641176c51f2d79 and later · before 7a8a3ff2815501f78f494808355ddf37e08647d0affected · git
- before 4.9not affected · semver
- 5.10.271 and later · up to and including 5.10.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-97490Sep 24, 2026 · affs: handle set_blocksize failures0Monitor
- ← EarlierCVE-2026-97491Sep 24, 2026 · net/rds: Don't sleep inside rds_ib_conn_path_shutdown0Monitor
- Later →CVE-2026-97493Sep 24, 2026 · drm/amdgpu: Bound GPIO I2C table entry count from VBIOS0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 026637b864b16dfae238e7e1accded820a3d7ae8 | Vendor (CNA) |
| Linux Linux | 60b96e44489d6775fe9cd8df619c29e0dc285c49 | Vendor (CNA) |
| Linux Linux | 6ef85dd9f8c62c9a465a32901d09475a114e67bd | Vendor (CNA) |
| Linux Linux | 6fb64029457cdcd77be546daf4c7c7cf04891857 | Vendor (CNA) |
| Linux Linux | 7a8a3ff2815501f78f494808355ddf37e08647d0 | Vendor (CNA) |
| Linux Linux | d2ea99884793c0a8d940073c3dddbb887590718f | Vendor (CNA) |
| Linux Linux | f27a5bda84ff3b0fea3de7572ff48e518e66cf5d | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | 6.6.161.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/60b96e44489d6775fe9cd8df619c29e0dc285c49
- git.kernel.org/stable/c/6ef85dd9f8c62c9a465a32901d09475a114e67bd
- git.kernel.org/stable/c/6fb64029457cdcd77be546daf4c7c7cf04891857
- git.kernel.org/stable/c/7a8a3ff2815501f78f494808355ddf37e08647d0
- git.kernel.org/stable/c/d2ea99884793c0a8d940073c3dddbb887590718f
- git.kernel.org/stable/c/f27a5bda84ff3b0fea3de7572ff48e518e66cf5d
Vendor advisories and official records. Exploit/PoC links are deliberately left out.