Vulnerability · Published Aug 10, 2026 · Assigned by Linux

CVE-2026-68408wifi: cfg80211: convert pmsr_free_wk to wiphy_work to fix deadlock

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 7% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 93.3% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official 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().

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-68408
Debian:13linux6.12.101-1DEBIAN-CVE-2026-68408
Debian:14linux7.1.6-1DEBIAN-CVE-2026-68408
Debian:12linux-6.126.12.101-1~deb12u1DEBIAN-CVE-2026-68408
Ubuntu:24.04:LTSlinux6.8.0-147.147UBUNTU-CVE-2026-68408
Ubuntu:26.04:LTSlinux7.0.0-38.38UBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-aws6.8.0-1067.70UBUNTU-CVE-2026-68408
Ubuntu:26.04:LTSlinux-aws7.0.0-1014.14UBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-aws-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-azure6.8.0-1071.79UBUNTU-CVE-2026-68408
Ubuntu:26.04:LTSlinux-azure7.0.0-1017.17UBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-azure-7.07.0.0-1017.17~24.04.1UBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1069.76UBUNTU-CVE-2026-68408
Ubuntu:26.04:LTSlinux-azure-fde7.0.0-1016.16UBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-azure-fde-7.07.0.0-1016.16~24.04.1UBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-gcp6.8.0-1071.79UBUNTU-CVE-2026-68408
Ubuntu:26.04:LTSlinux-gcp7.0.0-1014.14UBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-gcp-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-gke6.8.0-1066.74UBUNTU-CVE-2026-68408
Ubuntu:26.04:LTSlinux-gke7.0.0-1008.9UBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1052.56UBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-38.38~24.04.4UBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-ibm6.8.0-1067.68UBUNTU-CVE-2026-68408
Ubuntu:26.04:LTSlinux-ibm7.0.0-1015.15UBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-147.147.1UBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-68408
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-nvidia-7.07.0.0-1024.25~24.04.1UBUNTU-CVE-2026-68408
Ubuntu:26.04:LTSlinux-nvidia-bos7.0.0-2022.23UBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1036.39UBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-68408
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1015.15UBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-oracle6.8.0-1064.67UBUNTU-CVE-2026-68408
Ubuntu:26.04:LTSlinux-oracle7.0.0-1013.13UBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-oracle-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-68408
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-68408
Ubuntu:26.04:LTSlinux-realtime7.0.0-38.38.1UBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-68408
Ubuntu:26.04:LTSlinux-riscv7.0.0-38.38.1UBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-38.38.1~24.04.1UBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-68408
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-68408
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-68408

Affected products (as reported)

VendorProductVersions
Linux Linux 28d3551f8d8cb3aec7497894d94150fe84d20e5e – before efe47df4de5e3e19b0670c5f2f67bdc4c9dc02af37e776e2e0a523731e2470dce6d563f0e8632a40 – before 30c67926d41c456809857976cd3cd71b2290e0c1d32c07ef1880fe20cf4ab223dbfedc9c0b2816aa – before 21512b5f7a74fd18c996c22e6854efe57d570816a1b7a843f12a0c3e9d3a2ca607ce451916ef42cf – before 133684982dd0c24359fcc641d19d89cc17d6e5ef6dccbc9f3e1d38565dff7730d2b7d1e8b16c9b09 – before 0a77d9fb4d5c0e01306cd406ffdee8f1fe955c0e6dccbc9f3e1d38565dff7730d2b7d1e8b16c9b09 – before 2b0eab425e1f658d8fe1df7590e3b9af5959505e72b7ea786b8e570ae11149e9089859a4a8634a136.1.167 – before 6.1.191
Linux Linux 7.0

References