CVE-2024-36922: wifi: iwlwifi: read txq->read_ptr under lock
In the Linux kernel, the following vulnerability has been resolved:
wifi: iwlwifi: read txq->read_ptr under lock
If we read txq->read_ptr without lock, we can read the same
value twice, then obtain the lock, and reclaim from there
to two different places, but crucially reclaim the same
entry twice, resulting in the WARN_ONCE() a little later.
Fix that by reading txq->read_ptr under lock.
Security readout for executives and security teams
Plain-English summary
CVE-2024-36922 is a Linux kernel flaw in the Intel iwlwifi wireless driver. A race condition can make the driver reclaim the same transmit queue entry twice, triggering a kernel warning. The sources do not define business impact, CVSS severity, or confirmed exploitation.
Executive priority
Treat this as routine kernel maintenance unless local evidence shows Wi-Fi instability or vendor advisories raise severity. There is no sourced evidence of active exploitation or broad business impact in the provided bundle.
Technical view
The bug is in iwlwifi transmit queue handling. Reading txq->read_ptr without holding the lock can return the same value twice, after which reclaim can run against overlapping ranges and double-reclaim an entry. The upstream fix reads txq->read_ptr under lock.
Likely exposure
Exposure is likely limited to Linux systems using the iwlwifi driver, typically Intel Wi-Fi hardware, on affected kernel builds. The CVE data lists Linux kernel versions including 4.19, 5.15.209, 6.1.175, 6.6.31, 6.8.10, and 6.9 as affected.
Exploitation context
The bundle does not show CISA KEV listing, public exploitation, exploit maturity, or attacker requirements. It describes a concurrency bug and resulting WARN_ONCE condition, but does not prove remote, local, privilege escalation, or denial-of-service impact.
Researcher notes
Evidence is narrow. The root cause and fix are clear, but the bundle lacks CVSS, CWE, affected hardware matrix, triggerability details, and security impact analysis. Avoid assuming exploitability beyond the documented iwlwifi locking defect.
Mitigation direction
Check Linux vendor or distribution advisories for CVE-2024-36922 coverage.
Update affected kernels to builds containing the referenced stable iwlwifi fix.
Prioritize endpoints and appliances that use Intel Wi-Fi with iwlwifi loaded.
Track kernel changelogs for the listed stable commit identifiers.
Monitor fleet logs for repeated iwlwifi transmit queue warnings.
Validation and detection
Inventory Linux kernel versions across wireless-capable assets.
Confirm whether Intel Wi-Fi hardware and iwlwifi are present.
Compare installed kernel changelogs against CVE-2024-36922 and referenced commits.
After updating, verify the running kernel includes the vendor backport.
Review kernel logs for recurring WARN_ONCE or iwlwifi queue messages.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-36922 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.