CVE-2026-93149

wifi: mac80211_hwsim: avoid NULL skb in stop queue drain

N/A
Published: September 17, 2026 at 04:11 PM UTC
Updated: October 19, 2026 at 10:17 AM 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_hwsim: avoid NULL skb in stop queue drain mac80211_hwsim_stop() drops any frames left in data->pending. The loop currently checks skb_queue_empty() and then dequeues separately. That split is racy with TX status handling, which can remove a pending frame under the queue lock. If the last entry is removed after the empty check, skb_dequeue() returns NULL and the stop path passes that NULL skb to ieee80211_free_txskb(). Use skb_dequeue() as the loop condition instead. The dequeue result is the object that stop owns and frees, and a concurrent status completion that empties the queue simply makes the loop terminate.

Affected

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

5.10.475.12.145.135.4.1297019c9f385b264a2d6f685028268422d55087e3778bf3c6131488b00386acd9aff1ea4e6c44fa38ea9028333001f793b2724e8be42fce3336de2cf1cbd18de517923903a177508fc8813f44e717b1c00
Vendor states this is fixed in 158438cd6ad69d6dd7d871582c38baf22169fede (fixed)
Vendor states this is fixed in 1c2a4ab6efa26415dd131b8c222e7893fda03435 (fixed)
Vendor states this is fixed in 2817431a61557f46dc63077b7cc126bc906c242e (fixed)
Vendor states this is fixed in c40ba47f2ba1951cb32ea048667ed014d36a5749 (fixed)
Vendor states this is fixed in d131027054a8dd922dda01fe8d381abe5af4970b (fixed)
Vendor states this is fixed in e7fccad2c8e6ef6bbafe509c95869d161d0f466b (fixed)
Affected range stops below 5.11, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.13 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (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