wifi: cfg80211: use wiphy work for socket owner autodisconnect
CVE-2026-68404 · published 10 Aug 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-68404?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: bd2522b168847106c1885f0319a2833bdf88bf9a to < c55590e4c69e0fd194df6d20bc35381c201d99e1, bd2522b168847106c1885f0319a2833bdf88bf9a to < 4087a9ba4ece70297a4174afaa41c0b700302b65, bd2522b168847106c1885f0319a2833bdf88bf9a to < c2ddd180bbee766cf7359473d623423ea9485d93, bd2522b168847106c1885f0319a2833bdf88bf9a to < 6d6123fef5a4af175cc6b6b12a03dd0f3c240b79
- Linux Linux: 4.11
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/c55590e4c69e0fd194df6d20bc35381c201d99e1
- git.kernel.org/stable/c/4087a9ba4ece70297a4174afaa41c0b700302b65
- git.kernel.org/stable/c/c2ddd180bbee766cf7359473d623423ea9485d93
- git.kernel.org/stable/c/6d6123fef5a4af175cc6b6b12a03dd0f3c240b79
- git.kernel.org/stable/c/0c2ed186bbe14304415476d6707b747dddcd8583
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON