CVE-2026-98192
Last modified
CVE-2026-98192 is a vulnerability of currently unknown severity. 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.
Description
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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= fdf21cc3714939dd4327f3d664fe5863d15ccb31, < 3edabc965bcce49cbb2ec1c2b91f8a555a8ec8bd; >= fdf21cc3714939dd4327f3d664fe5863d15ccb31, < 2bddc5d088cf430ecd913020472f1def32a36a3d; >= fdf21cc3714939dd4327f3d664fe5863d15ccb31, < c0df0878e9110909cf0bec6080d72d36401a0c89; >= fdf21cc3714939dd4327f3d664fe5863d15ccb31, < d9be5e75530772fc31637070d51e5717d6aeaa2a |
| Linux | Linux | 5.10 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-98192?
How severe is CVE-2026-98192?
How do I fix CVE-2026-98192?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-98186In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98187In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98188In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98189In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98190In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98191In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98193In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98194In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98195In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98196In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98197In the Linux kernel, the following vulnerability has been re…7
- CVE-2026-98198In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-98192?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
