CVE-2026-68404
Last modified
CVE-2026-68404 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: use wiphy work for socket owner autodisconnect nl80211_netlink_notify() walks the cfg80211 wireless device list when a NETLINK_GENERIC socket is released. If the socket owns a connection, the notifier queues the embedded wdev->disconnect_wk work item. That work is a plain work_struct today.
Description
In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: use wiphy work for socket owner autodisconnect nl80211_netlink_notify() walks the cfg80211 wireless device list when a NETLINK_GENERIC socket is released. If the socket owns a connection, the notifier queues the embedded wdev->disconnect_wk work item. That work is a plain work_struct today. NETDEV_GOING_DOWN cancels it, but a NETLINK_URELEASE notifier that already observed conn_owner_nlportid can queue it after that cancel returns. _cfg80211_unregister_wdev() then removes the wdev from the list and waits for RCU readers, but synchronize_net() does not drain work queued by such a reader. Make the autodisconnect work a wiphy_work instead. The callback already needs the wiphy mutex, and wiphy_work runs under that mutex. This lets teardown cancel pending autodisconnect work while holding the mutex, without a cancel_work_sync() vs. worker locking concern. Also cancel the wiphy work after list_del_rcu() and synchronize_net(). Any NETLINK_URELEASE notifier that had already reached the wdev list has then either queued the work and it is removed, or can no longer find the wdev.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= bd2522b168847106c1885f0319a2833bdf88bf9a, < 6d6123fef5a4af175cc6b6b12a03dd0f3c240b79; >= bd2522b168847106c1885f0319a2833bdf88bf9a, < 0c2ed186bbe14304415476d6707b747dddcd8583 |
| Linux | Linux | 4.11 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-68404?
How severe is CVE-2026-68404?
How do I fix CVE-2026-68404?
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-68399In the Linux kernel, the following vulnerability has been re…
- CVE-2026-6840Missing bounds validation for operator could allow out of r…5.5
- CVE-2026-68400In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68401In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68402In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68403In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68405In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68406In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68407In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68408In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68409In the Linux kernel, the following vulnerability has been re…
- CVE-2026-6841Request Tracker is vulnerable to a reflected cross-site scri…6.1
Are you affected by CVE-2026-68404?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
