wifi: mac80211: don't call ieee80211_handle_reconfig_failure when not needed
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.271, 5.15.222, 6.1.189, 6.12.111, 6.18.53, 6.6.160
- CVEs
- CVE-2026-97492
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 17:24 UTC · Revision 1
Source evidence
wifi: mac80211: don't call ieee80211_handle_reconfig_failure when not needed
core-osv · Original sourcePublished 24 Sept 2026, 16:04 UTC
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.
osv:CVE-2026-97492
Kernel
Fixed versions: 5.10.271, 5.15.222, 6.1.189, 6.6.160, 6.12.111, 6.18.53
Complete source record
{
"id": "7613d5c57ed20b7c8dc42e2775055cf8489399420d8884a125fc20f746862337",
"url": "https://osv.dev/vulnerability/CVE-2026-97492",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "wifi: mac80211: don't call ieee80211_handle_reconfig_failure when not needed",
"summary": "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.",
"evidence": "osv:CVE-2026-97492",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.271",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.222",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.189",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.160",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.111",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.53",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-97492",
"aliases": [
"CVE-2026-97492"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "167e33f4f68cc8e4e3bdaf6d43641176c51f2d79"
},
{
"fixed": "026637b864b16dfae238e7e1accded820a3d7ae8"
},
{
"fixed": "6ef85dd9f8c62c9a465a32901d09475a114e67bd"
},
{
"fixed": "f27a5bda84ff3b0fea3de7572ff48e518e66cf5d"
},
{
"fixed": "d2ea99884793c0a8d940073c3dddbb887590718f"
},
{
"fixed": "60b96e44489d6775fe9cd8df619c29e0dc285c49"
},
{
"fixed": "6fb64029457cdcd77be546daf4c7c7cf04891857"
},
{
"fixed": "7a8a3ff2815501f78f494808355ddf37e08647d0"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-97492.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.9.0"
},
{
"fixed": "5.10.271"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.222"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.189"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.160"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.111"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.53"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-97492.json"
}
}
],
"modified": "2026-10-28T02:30:30.714979650Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/026637b864b16dfae238e7e1accded820a3d7ae8",
"https://git.kernel.org/stable/c/60b96e44489d6775fe9cd8df619c29e0dc285c49",
"https://git.kernel.org/stable/c/6ef85dd9f8c62c9a465a32901d09475a114e67bd",
"https://git.kernel.org/stable/c/6fb64029457cdcd77be546daf4c7c7cf04891857",
"https://git.kernel.org/stable/c/7a8a3ff2815501f78f494808355ddf37e08647d0",
"https://git.kernel.org/stable/c/d2ea99884793c0a8d940073c3dddbb887590718f",
"https://git.kernel.org/stable/c/f27a5bda84ff3b0fea3de7572ff48e518e66cf5d",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/97xxx/CVE-2026-97492.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-97492",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/97xxx/CVE-2026-97492.json"
}
},
"related_cves": [
{
"value": "CVE-2026-97492",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 497802,
"published_at": "2026-09-24T16:04:40.294+00:00"
}