Skip to main content
VulnerabilityPublished Updated

CVE-2026-68404: Linux kernel · wifi: cfg80211: use wiphy work for socket owner autodisconnect

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High · fixed in c55590e4c69e0fd194df6d20bc35381c201d99e1 : patch Linux kernel soon.

Data as of 26 Oct 2026, 17:30 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in c55590e4c69e0fd194df6d20bc35381c201d99e1, c2ddd180bbee766cf7359473d623423ea9485d93, 4087a9ba4ece70297a4174afaa41c0b700302b65 +2
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ bd2522b168847106c1885f0319a2833bdf88bf9a, < c55590e4c69e0fd194df6d20bc35381c201d99e1
Fixed in
  • c55590e4c69e0fd194df6d20bc35381c201d99e1
LinuxLinuxAffected
  • ≥ bd2522b168847106c1885f0319a2833bdf88bf9a, < c2ddd180bbee766cf7359473d623423ea9485d93
Fixed in
  • c2ddd180bbee766cf7359473d623423ea9485d93
LinuxLinuxAffected
  • ≥ bd2522b168847106c1885f0319a2833bdf88bf9a, < 4087a9ba4ece70297a4174afaa41c0b700302b65
Fixed in
  • 4087a9ba4ece70297a4174afaa41c0b700302b65
LinuxLinuxAffected
  • ≥ bd2522b168847106c1885f0319a2833bdf88bf9a, < 6d6123fef5a4af175cc6b6b12a03dd0f3c240b79
Fixed in
  • 6d6123fef5a4af175cc6b6b12a03dd0f3c240b79
LinuxLinuxAffected
  • ≥ bd2522b168847106c1885f0319a2833bdf88bf9a, < 0c2ed186bbe14304415476d6707b747dddcd8583
Fixed in
  • 0c2ed186bbe14304415476d6707b747dddcd8583
LinuxLinuxAffected
  • =4.11
Fixed in–

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.

References

Community reviews

Loading reviews…