CVE-2026-68405

wifi: mac80211: free AP_VLAN bc_buf SKBs outside IRQ lock

N/A
Published: August 10, 2026 at 12:04 PM UTC
Updated: August 19, 2026 at 05:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: free AP_VLAN bc_buf SKBs outside IRQ lock ieee80211_do_stop() removes AP_VLAN packets from the parent AP ps->bc_buf while holding ps->bc_buf.lock with IRQs disabled. It then calls ieee80211_free_txskb() before dropping the lock. ieee80211_free_txskb() is not just a passive SKB release. For SKBs with TX status state it can report a dropped frame through cfg80211/nl80211, and that path can reach netlink tap transmit. This is the same reason the pending queue cleanup in ieee80211_do_stop() already unlinks SKBs under the queue lock and frees them after IRQ state is restored. The buggy scenario involves two paths, with each column showing the order within that path: AP_VLAN management TX: AP_VLAN stop: 1. attach ACK-status state 1. clear the running state 2. queue a multicast SKB on 2. take ps->bc_buf.lock with IRQs parent ps->bc_buf disabled 3. unlink the AP_VLAN SKB 4. call ieee80211_free_txskb() Unlink matching AP_VLAN SKBs from ps->bc_buf under the existing lock, but move them to a local free queue. Drop the lock and restore IRQ state before calling ieee80211_free_txskb(). WARNING: kernel/softirq.c:430 at __local_bh_enable_ip

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.9 ≤ v < 5.10.2653.9 ≤ v < 5.15.2163.9 ≤ v < 6.1.1833.9 ≤ v < 6.12.1013.9 ≤ v < 6.18.423.9 ≤ v < 6.6.1483.9 ≤ v < 7.1.63.9 ≤ v < 7.23.9397a7a24ef8c2967a3e8090013f9c54714110c48
Vendor states this is fixed in 0d2619e708e2ef02ba1c91642ea261d3f19d8f9a (fixed)
Vendor states this is fixed in 4b8abf43bf34791c99d99dc3be13f897adefc461 (fixed)
Vendor states this is fixed in 659a81b62a61440b85e02c09903be861ae7679e5 (fixed)
Vendor states this is fixed in 962f755a47d7ec3bbf6c709697d7f4c5f798441d (fixed)
Vendor states this is fixed in a424985c3ef2a87ce6057a853e18d0c441a86be8 (fixed)
Vendor states this is fixed in aa01ef0ebbc3289154229ef58e65baf289eb9789 (fixed)
Vendor states this is fixed in be9dfcb0654c1f6c0fce7ba2a909683bb6f1e0ef (fixed)
Vendor states this is fixed in f3858d5b1432098c1936e03d6e03dd0e33facf60 (fixed)
Vendor states this is fixed in 3.9 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card