CVE-2026-68414: wifi: cfg80211: cancel sched scan results work on unregister

Published Aug 10, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

wifi: cfg80211: cancel sched scan results work on unregister

cfg80211schedscanresults() can queue rdev->schedscanreswk from a driver result notification while a scheduled scan request is present. The work callback recovers the containing cfg80211registereddevice and then locks the wiphy and walks the scheduled-scan request list.

wiphyunregister() already makes the wiphy unreachable and drains rdev work items before cfg80211devfree() can release the object, but it does not drain schedscanreswk. A queued or running result work item can therefore cross the unregister/free boundary and access freed rdev state.

The buggy scenario involves two paths, with each column showing the order within that path:

scheduled-scan result path: unregister/free path: 1. cfg80211schedscanresults() 1. interface teardown stops and queues rdev->schedscanreswk. removes the scheduled scan request. 2. cfg80211wq starts the work 2. wiphyunregister() drains other item and recovers rdev. rdev work items. 3. The worker locks rdev->wiphy 3. cfg80211devfree() destroys and and walks rdev state. frees rdev.

Cancel schedscanreswk in wiphyunregister() alongside the other rdev work items. cancelworksync() removes a pending result notification and waits for an already running callback, so cfg80211devfree() cannot free rdev while this work item is still active.

Validation reproduced this kernel report: BUG: KASAN: use-after-free in cfg80211schedscanresultswk+0x4a6/0x530 Workqueue: cfg80211 cfg80211schedscanresultswk [cfg80211] Read of size 8 Call trace: dumpstacklvl+0x66/0xa0 printreport+0xce/0x630 cfg80211schedscanresultswk+0x4a6/0x530 srsoaliasreturnthunk+0x5/0xfbef5 virtaddrvalid+0x224/0x430 kasanreport+0xac/0xe0 lockdephardirqsonprepare+0xea/0x1a0 processonework+0x8d0/0x18f0 (kernel/workqueue.c:3212) lockisheldtype+0x8f/0x100 workerthread+0x5ad/0xfd0 kthreadparkme+0xc6/0x200 kthread+0x31e/0x410 tracehardirqson+0x1a/0x170 retfromfork+0x576/0x810 switchto+0x57e/0xe20 switchtoasm+0x33/0x70 retfromforkasm+0x1a/0x30

Affected Software

1 affected component
Linux Kernel

Event History

Aug 10, 2026
CVE Published
via MITRE·12:04 PM
Data Sourced
via MITRE·12:04 PM
Description
Data Sourced
via NVD·01:20 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-68414?

CVE-2026-68414 has a risk score of 40, indicating a significant vulnerability in the Linux kernel.

2

How do I fix CVE-2026-68414?

To resolve CVE-2026-68414, update to the latest patched version of the Linux kernel that addresses this vulnerability.

3

What impact does CVE-2026-68414 have on systems?

CVE-2026-68414 can lead to potential use-after-free conditions, which may allow attackers to execute arbitrary code or cause a system crash.

4

Is CVE-2026-68414 exploitable remotely?

CVE-2026-68414 may be exploitably in specific conditions depending on how network drivers handle scheduled scans.

5

What systems are affected by CVE-2026-68414?

CVE-2026-68414 affects Linux kernel versions prior to the fix that addresses this vulnerability in the cfg80211 module.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203