CVE-2026-68408Patch

LOW

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch affected systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: convert pmsr_free_wk to wiphy_work to fix deadlock When a netlink socket that owns a PMSR session is closed, cfg80211_release_pmsr() clears the request's nl_portid and queues pmsr_free_wk to call cfg80211_pmsr_process_abort() asynchronously. If the interface tears down concurrently, cfg80211_pmsr_wdev_down() is called under wiphy_lock and calls cancel_work_sync(&pmsr_free_wk) to wait for any running work. The work function acquires wiphy_lock via guard(wiphy) before calling process_abort. This is a deadlock: wdev_down holds wiphy_lock and blocks inside cancel_work_sync(); pmsr_free_wk blocks trying to acquire that same wiphy_lock. Neither thread can proceed. The same deadlock is reachable from cfg80211_leave_locked(), which calls cfg80211_pmsr_wdev_down() for all interface types under wiphy_lock. Fix this by converting pmsr_free_wk from a plain work_struct to a wiphy_work. The wiphy_work dispatcher holds wiphy_lock when running work items, so the explicit guard(wiphy) in the work function is no longer needed. wiphy_work_cancel() can be called safely while holding wiphy_lock - since wiphy_lock prevents the work from running concurrently, wiphy_work_cancel() never blocks, eliminating the deadlock. Remove the cancel_work_sync() for pmsr_free_wk from the NETDEV_GOING_DOWN handler. cfg80211_leave(), called unconditionally just before it, already cancels any pending work under wiphy_lock via wiphy_work_cancel() inside cfg80211_pmsr_wdev_down().

0.5/ 10 priority

Sources & remediation

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

STABLE

Threat summary

  • Patch or workaround signal is available
  • 2 mentions across 2 observed days
  • Momentum state: stable

What's happening

  • Patch or workaround mentioned in 2 signals
  • Technical details provided in 1 signal
  • Peaked 1d ago at 1 mentions (2026-08-10); latest day: 1
  • 2 total mentions across 2 days

Deep dive

Activity timeline2 mentions / 2d
00111Mentions · 2026-08-10: 1Mentions · 2026-08-11: 1Patch / Workaround · 2026-08-10: 1Patch / Workaround · 2026-08-11: 1Technical Details · 2026-08-11: 108-1008-11
Signal classification1 categories
Patch
2100.0%
Referenced assets2 URLs
Full discourse2 posts
  • Windows Forum@windowsforum
    Patch

    🐧 CVE-2026-68408 can deadlock Linux Wi‑Fi teardown during peer measurements. Linux admins: patch up. Windows users: your Wi‑Fi isn’t the culprit this time—enjoy the rare exemption. https://windowsforum.com/security-alerts.84/cve-2026-68408-linux-wi-fi-pmsr-teardown-deadlock-fix.442408/?utm_source=x&utm_medium=social&utm_campaign=news_node84 #LinuxKernel #WiFiSecurity #Cfg80211 #Cve202668408 https://t.co/eUlpN7C2Ae

    Post summary

    The post announces that CVE-2026-68408 causes a deadlock in Linux Wi‑Fi teardown and urges Linux administrators to apply the patch; no active exploitation or PoC is reported.

    0000067
    1.3K followersView on X
  • Vulmon Vulnerability Feed@VulmonFeeds
    Patch

    CVE-2026-68408 In the Linux kernel, the following vulnerability has been resolved: wifi https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-68408

    Post summary

    The post notes that CVE-2026-68408, affecting the Linux kernel’s wifi component, has been resolved—implying a patch has been applied, but no additional exploit or technical details are provided.

    00000109
    4.1K followersView on X

Explore more