Loading vulnerability…
CVE-2024-36922 is a race condition in the Linux kernel iwlwifi wireless driver’s transmit-queue reclamation handling. The driver read the transmit queue read pointer, txq->read_ptr, before acquiring the required lock. Concurrent activity could cause the same pointer value to be observed twice; after locking, reclamation could then proceed toward two distinct queue positions while reclaiming an already reclaimed entry a second time. The upstream correction moves the txq->read_ptr read into the protected critical section.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A locking flaw in the Linux kernel iwlwifi driver's access to txq->read_ptr.
Linux kernel Intel iwlwifi race condition caused by accessing txq->read_ptr without required locking.
Linux kernel iwlwifi driver race/concurrency flaw involving txq->read_ptr access without the required lock.
A resolved Linux kernel iwlwifi Wi-Fi driver synchronization issue involving reading txq->read_ptr without the required lock. The issue was addressed through Red Hat security advisories for supported RHEL 8 and RHEL 9 releases.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.