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-93804wifi: mac80211: ibss: wait for in-flight TX on disconnect

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: ibss: wait for in-flight TX on disconnect While leaving an IBSS in ieee80211_ibss_disconnect() mac80211 flushes stations, turns the carrier off and immediately tells the driver to leave as well. While there may be synchronize_net() in station flush and in this code later, packets can still be transmitted due to cross-CPU race conditions after carrier off is set. Therefore, it's possible for a race to happen where a TX to the driver occurs while or after telling it to leave the IBSS. This can be confusing to drivers, and in the case of iwlwifi leads to an attempt to use invalid queues. Move netif_carrier_off() to occur before sta_info_flush() during IBSS disconnect, and add synchronize_net() if flushing didn't, so that the synchronize_net() always happens between turning the carrier off and telling the driver, avoiding this race.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 36 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.17% · top 93% 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 86a2ea4134b48f6371103cfceb521bf2d2bf76cd – < 47185b5dbac264e7eb48c6d44368be6bfec17085
    • affected 86a2ea4134b48f6371103cfceb521bf2d2bf76cd – < 8e4a07ed82bae5d13525770880dc6dfd27f9bccd
    • affected 86a2ea4134b48f6371103cfceb521bf2d2bf76cd – < 20a3fb5e1a95caa34896853ca17a50d21c754969
    • affected 86a2ea4134b48f6371103cfceb521bf2d2bf76cd – < b3451e6971248250312ad32dd7f63cc9f0a925f5
    • affected 86a2ea4134b48f6371103cfceb521bf2d2bf76cd – < d0e69d9afa59b93c30294eba89b1f15f69e91105
  • Linux · Linux

    • affected 3.3
    • unaffected < 3.3
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .