Linux kernel use-after-free in ath9k channel-context timers
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
wifi: ath9k: delete channel-context timers on deinit
ath9k_deinit_channel_context() cancels chanctx_work but does not delete the offchannel and sched timers set up by ath9k_init_channel_context(). If either timer fires after deinit (e.g. during driver unload or suspend), it accesses sc->sc_ah which may already be freed by ath9k_hw_deinit(), causing a use-after-free.
Delete both timers with timer_shutdown_sync() before cancelling the work item.
From the CVE record · Linux
The Linux kernel's ath9k driver does not shut down two channel-context timers during deinitialization. If either fires afterward, such as during driver unload or suspend, it can access freed memory. The input does not specify an attacker, access requirements, or user interaction.
Engineers running Linux kernels with the ath9k driver should check their kernel; affected versions are not specified.