Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-93149wifi: mac80211_hwsim: avoid NULL skb in stop queue drain

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected bd18de517923903a177508fc8813f44e717b1c00 – < d131027054a8dd922dda01fe8d381abe5af4970b
    • affected bd18de517923903a177508fc8813f44e717b1c00 – < c40ba47f2ba1951cb32ea048667ed014d36a5749
    • affected bd18de517923903a177508fc8813f44e717b1c00 – < 2817431a61557f46dc63077b7cc126bc906c242e
    • affected bd18de517923903a177508fc8813f44e717b1c00 – < e7fccad2c8e6ef6bbafe509c95869d161d0f466b
    • affected bd18de517923903a177508fc8813f44e717b1c00 – < 1c2a4ab6efa26415dd131b8c222e7893fda03435
    • affected bd18de517923903a177508fc8813f44e717b1c00 – < 158438cd6ad69d6dd7d871582c38baf22169fede
    • affected 78bf3c6131488b00386acd9aff1ea4e6c44fa38e
    • affected a9028333001f793b2724e8be42fce3336de2cf1c
    • affected 7019c9f385b264a2d6f685028268422d55087e37
    • affected 5.4.129 – < 5.5
    • affected 5.10.47 – < 5.11
    • affected 5.12.14 – < 5.13
  • Linux · Linux

    • affected 5.13
    • unaffected < 5.13
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93149 badge
[![CVE-2026-93149](https://cveledger.app/badge/CVE-2026-93149.svg)](https://cveledger.app/cve/CVE-2026-93149)

Record last updated .