CVE-2026-93804
Last modified
CVE-2026-93804 is a vulnerability of currently unknown severity. 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.
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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 86a2ea4134b48f6371103cfceb521bf2d2bf76cd, < 20a3fb5e1a95caa34896853ca17a50d21c754969; >= 86a2ea4134b48f6371103cfceb521bf2d2bf76cd, < b3451e6971248250312ad32dd7f63cc9f0a925f5; >= 86a2ea4134b48f6371103cfceb521bf2d2bf76cd, < d0e69d9afa59b93c30294eba89b1f15f69e91105 |
| Linux | Linux | 3.3 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-93804?
How severe is CVE-2026-93804?
How do I fix CVE-2026-93804?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-93799In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-9380A security vulnerability has been detected in Edimax BR-6675…8.8
- CVE-2026-93800In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93801In the Linux kernel, the following vulnerability has been re…7
- CVE-2026-93802In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93803In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93805In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93806In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-93807In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93808In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93809In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9381A vulnerability was detected in Edimax BR-6675nD 1.12. Affec…8.8
Are you affected by CVE-2026-93804?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
