CVE-2023-54288: 
Linux Kernel vulnerability analysis and mitigation

CVE-2023-54288 is a deadlock vulnerability in the Linux kernel's mac80211 Wi-Fi subsystem, specifically within the ieee80211_tx_dequeue() function. The flaw arises from a spinlock (queue_stop_reason_lock) that did not disable interrupts, allowing an asynchronous interrupt to re-acquire the same lock on the same CPU core, causing a deadlock. It affects the Linux kernel and was published on December 30, 2025. The vulnerability is estimated as Medium severity, with an EPSS score of 0.00017 (Feedly, CVE.org).

The root cause is a missing interrupt-disabling flag in a spin_lock() call within ieee80211_tx_dequeue() in the Linux kernel's mac80211 subsystem (CWE-667: Improper Locking). The locking sequence acquires local->queue_stop_reason_lock without disabling interrupts; if an interrupt fires between spin_lock() and spin_unlock(), the interrupt handler attempts to acquire the same lock on the same CPU, resulting in a deadlock. This is particularly reproducible under ftracetest or on single-CPU/single-core systems. The fix replaces the plain spin_lock/spin_unlock pair with interrupt-safe variants (spin_lock_irqsave/spin_unlock_irqrestore) (Feedly, Kernel Patch 1, Kernel Patch 2).

Successful triggering of this vulnerability results in a denial-of-service condition: either a costly CPU and Wi-Fi device reset or a complete system hang, particularly on single-CPU or single-core configurations. There is no evidence of confidentiality or integrity impact; the primary consequence is loss of availability of the affected system's Wi-Fi functionality and potentially the entire kernel. The vulnerability is locally triggered through normal Wi-Fi traffic processing and does not enable privilege escalation or remote code execution (Feedly).

The fix has been committed to the Linux kernel stable tree, replacing the non-interrupt-safe spinlock calls in ieee80211_tx_dequeue() with interrupt-safe variants. Administrators should apply the relevant stable kernel patches (commits 6df3eafa31b3, c79d794a2cd7, and ef6e1997da63) or upgrade to a patched kernel version that includes these fixes. Linux distribution vendors (e.g., Red Hat) are tracking this issue and may release updated kernel packages; users should monitor their distribution's security advisories and apply updates promptly (Kernel Patch 1, Kernel Patch 2, Kernel Patch 3).