wifi: wcn36xx: Fix potential use-after-free in TX ack timer teardown
In the Linux kernel, the following vulnerability has been resolved: wifi: wcn36xx: Fix potential use-after-free in TX ack timer teardown wcn36xx_dxe_deinit() tears down the TX ack timer with timer_delete(), which only dequeues the timer and does not wait for a callback that is already executing; the preceding free_irq() calls synchronize the interrupt handlers only. The callback, wcn36xx_dxe_tx_timer(), can therefore be running past the teardown and use the wcn freed along with the ieee80211_hw in wcn36xx_remove(): it takes wcn->dxe_lock, reads wcn->tx_ack_skb and passes wcn->hw to ieee80211_tx_status_irqsafe(). Fix this by using timer_shutdown_sync(), which waits for a running callback and also prevents the timer from being rearmed again. The timer is set up again by wcn36xx_dxe_init() on the next start, so the start/stop cycle is unaffected. This issue was found by an in-house static analysis tool.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.273, 5.15.224, 6.1.191, 6.12.112, 6.18.54, 6.6.160, 7.2.8
- CVEs
- CVE-2026-98192
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 02:20 UTC · Revision 1
Source evidence
wifi: wcn36xx: Fix potential use-after-free in TX ack timer teardown
core-osv · Original sourcePublished 6 Oct 2026, 08:44 UTC
In the Linux kernel, the following vulnerability has been resolved: wifi: wcn36xx: Fix potential use-after-free in TX ack timer teardown wcn36xx_dxe_deinit() tears down the TX ack timer with timer_delete(), which only dequeues the timer and does not wait for a callback that is already executing; the preceding free_irq() calls synchronize the interrupt handlers only. The callback, wcn36xx_dxe_tx_timer(), can therefore be running past the teardown and use the wcn freed along with the ieee80211_hw in wcn36xx_remove(): it takes wcn->dxe_lock, reads wcn->tx_ack_skb and passes wcn->hw to ieee80211_tx_status_irqsafe(). Fix this by using timer_shutdown_sync(), which waits for a running callback and also prevents the timer from being rearmed again. The timer is set up again by wcn36xx_dxe_init() on the next start, so the start/stop cycle is unaffected. This issue was found by an in-house static analysis tool.
osv:CVE-2026-98192
Kernel
Fixed versions: 5.10.273, 5.15.224, 6.1.191, 6.6.160, 6.12.112, 6.18.54, 7.2.8
Complete source record
{
"id": "111d161bdf3ec8339b752746237c9f794187906d0dad14fc11d7b82d0766f457",
"url": "https://osv.dev/vulnerability/CVE-2026-98192",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "wifi: wcn36xx: Fix potential use-after-free in TX ack timer teardown",
"summary": "In the Linux kernel, the following vulnerability has been resolved: wifi: wcn36xx: Fix potential use-after-free in TX ack timer teardown wcn36xx_dxe_deinit() tears down the TX ack timer with timer_delete(), which only dequeues the timer and does not wait for a callback that is already executing; the preceding free_irq() calls synchronize the interrupt handlers only. The callback, wcn36xx_dxe_tx_timer(), can therefore be running past the teardown and use the wcn freed along with the ieee80211_hw in wcn36xx_remove(): it takes wcn->dxe_lock, reads wcn->tx_ack_skb and passes wcn->hw to ieee80211_tx_status_irqsafe(). Fix this by using timer_shutdown_sync(), which waits for a running callback and also prevents the timer from being rearmed again. The timer is set up again by wcn36xx_dxe_init() on the next start, so the start/stop cycle is unaffected. This issue was found by an in-house static analysis tool.",
"evidence": "osv:CVE-2026-98192",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.273",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.224",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.191",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.160",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.112",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.54",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.8",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-98192",
"aliases": [
"CVE-2026-98192"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "fdf21cc3714939dd4327f3d664fe5863d15ccb31"
},
{
"fixed": "915298dbb766d2311b0822ab6ef24780def0bd53"
},
{
"fixed": "e7f265d507ee55017b67ef4722df884468be1113"
},
{
"fixed": "7ce1e55a439968a298a63d3199cb1c2636429746"
},
{
"fixed": "15e59e377facc87ce82228279d88efaa89fdbca5"
},
{
"fixed": "3edabc965bcce49cbb2ec1c2b91f8a555a8ec8bd"
},
{
"fixed": "2bddc5d088cf430ecd913020472f1def32a36a3d"
},
{
"fixed": "c0df0878e9110909cf0bec6080d72d36401a0c89"
},
{
"fixed": "d9be5e75530772fc31637070d51e5717d6aeaa2a"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98192.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.10.0"
},
{
"fixed": "5.10.273"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.224"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.191"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.160"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.112"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.54"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.2.8"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98192.json"
}
}
],
"modified": "2026-11-01T02:30:49.519557442Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/15e59e377facc87ce82228279d88efaa89fdbca5",
"https://git.kernel.org/stable/c/2bddc5d088cf430ecd913020472f1def32a36a3d",
"https://git.kernel.org/stable/c/3edabc965bcce49cbb2ec1c2b91f8a555a8ec8bd",
"https://git.kernel.org/stable/c/7ce1e55a439968a298a63d3199cb1c2636429746",
"https://git.kernel.org/stable/c/915298dbb766d2311b0822ab6ef24780def0bd53",
"https://git.kernel.org/stable/c/c0df0878e9110909cf0bec6080d72d36401a0c89",
"https://git.kernel.org/stable/c/d9be5e75530772fc31637070d51e5717d6aeaa2a",
"https://git.kernel.org/stable/c/e7f265d507ee55017b67ef4722df884468be1113",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98192.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-98192",
"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/98xxx/CVE-2026-98192.json"
}
},
"related_cves": [
{
"value": "CVE-2026-98192",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 499607,
"published_at": "2026-10-06T08:44:32.912+00:00"
}