PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-93804 Linux CVE debrief

A race condition vulnerability in the Linux kernel's mac80211 IBSS disconnect handling could lead to drivers receiving invalid queue requests. The issue arises when the carrier is turned off after station flushing, allowing for in-flight TX packets to be transmitted. To address this, the carrier off operation is moved before station flushing, and synchronize_net() is added if flushing didn't occur. This change ensures that the synchronize_net() always happens between turning the carrier off and telling the driver to leave the IBSS, avoiding the race condition.

Vendor
Linux
Product
Unknown
CVSS
Unknown
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-24
Original CVE updated
2026-09-25
Advisory published
2026-09-24
Advisory updated
2026-09-25

Who should care

Linux kernel maintainers, Linux distribution vendors, and users of Linux-based systems, especially those using wireless networking, should assess exposure and apply patches or updates as needed.

Why it matters

A race condition vulnerability in the Linux kernel's mac80211 IBSS disconnect handling could lead to drivers receiving invalid queue requests, potentially causing system instability or crashes.

  • Verify Linux kernel versions and configurations for exposure
  • Apply patches or updates provided by the Linux kernel maintainers
  • Monitor system logs for potential indicators of compromise

Technical summary

The Linux kernel's mac80211 IBSS disconnect handling has a race condition vulnerability. When leaving an IBSS, mac80211 flushes stations, turns the carrier off, and tells the driver to leave. However, due to cross-CPU race conditions, packets can still be transmitted after the carrier is turned off. This can cause drivers to receive invalid queue requests, leading to potential issues. The fix involves moving the netif_carrier_off() operation before sta_info_flush() and adding synchronize_net() if flushing didn't occur.

Defensive priority

Medium

Recommended defensive actions

  • Review Linux kernel versions and configurations for exposure
  • Apply patches or updates provided by the Linux kernel maintainers
  • Monitor system logs for potential indicators of compromise
  • Verify driver functionality and queue management
  • Perform an inventory of assets using Linux-based systems, especially those using wireless networking
  • Establish a rollback plan for changes made to remediate this vulnerability
  • Track and verify the effectiveness of applied patches or updates

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but the scope of affected systems and versions is not explicitly stated. The Linux kernel patch commits are referenced, indicating that the fix is available.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-93804 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-93804

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-93804 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-93804

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/20a3fb5e1a95caa34896853ca17a50d21c754969

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/b3451e6971248250312ad32dd7f63cc9f0a925f5

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/d0e69d9afa59b93c30294eba89b1f15f69e91105

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.