wifi: ath9k: delay all of ath9k_wmi_event_tasklet() until init is complete
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.214, 5.15.153, 5.17, 6.1.83, 6.6.23, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: delay all of ath9k_wmi_event_tasklet() until init is complete The ath9k_wmi_event_tasklet() used in ath9k_htc assumes that all the data structures have been fully initialised by the time it runs. However, because of the order in which things are initialised, this is not guaranteed to be the case, because the device is exposed to the USB subsystem before the ath9k driver initialisation is completed. We already committed a partial fix for this in commit: 8b3046abc99e ("ath9k_htc: fix NULL pointer dereference at ath9k_htc_tx_get_packet()") However, that commit only aborted the WMI_TXSTATUS_EVENTID command in the event tasklet, pairing it with an "initialisation complete" bit in the TX struct. It seems syzbot managed to trigger the race for one of the other commands as well, so let's just move the existing synchronisation bit to cover the whole tasklet (setting it at the end of ath9k_htc_probe_device() instead of inside ath9k_tx_init()).
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 78c8397132dd4735ac6a7b5a651302f0b9f264ad · fixed in 1bc5461a21c56a36e2a7d81e152b90ce019a3905; From 735aefae7b68025cd04c482a940c0f6fc6797a63 · fixed in f8ff4b4df71e87f609be0cc37d92e918107f9b90; From 8b3046abc99eefe11438090bcc4ec3a3994b55d0 · fixed in 74d0639261dd795dce958d1b14815bdcbb48a715; From 8b3046abc99eefe11438090bcc4ec3a3994b55d0 · fixed in a015fbf698c8957aa5fbeefc5c59dd2cf3107298; From 8b3046abc99eefe11438090bcc4ec3a3994b55d0 · fixed in ac90e22e735bac44f74b5161fb096fbeb0ff8bc2; From 8b3046abc99eefe11438090bcc4ec3a3994b55d0 · fixed in 4afa0246656d5680c8a4c3fb37ba6570c4ab819b; From 8b3046abc99eefe11438090bcc4ec3a3994b55d0 · fixed in 24355fcb0d4cbcb6ddda262596558e8cfba70f11; From 5.10.136 · fixed in 5.10.214; From 5.15.17 · fixed in 5.15.153; From 5.16.3 · fixed in 5.17
- Linux Linux
5.17
- KernelLinux
fixed in 5.10.214; From 5.11.0 · fixed in 5.15.153; From 5.16.0 · fixed in 6.1.83; From 5.17.0 · fixed in 6.6.23; From 6.2.0 · fixed in 6.7.11; From 6.7.0 · fixed in 6.8.2
References 7
git.kernel.org
- stable/c/1bc5461a21c56a36e2a7d81e152b90ce019a3905
- stable/c/f8ff4b4df71e87f609be0cc37d92e918107f9b90
- stable/c/74d0639261dd795dce958d1b14815bdcbb48a715
- stable/c/a015fbf698c8957aa5fbeefc5c59dd2cf3107298
- stable/c/ac90e22e735bac44f74b5161fb096fbeb0ff8bc2
- stable/c/4afa0246656d5680c8a4c3fb37ba6570c4ab819b
- stable/c/24355fcb0d4cbcb6ddda262596558e8cfba70f11