Skip to content
statance
MenuClose
unknown

CVE-2026-99452

wifi: ath9k: delete channel-context timers on deinit

Published 19 Nov 2026 · Source updated 19 Nov 2026 · Retrieved 2026-11-19 15:23 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

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.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
LinuxLinuxaffected: 705d0bf83dbef34d49927d3bf05c6d497f42e8b0 to < c2c268ec920867b42ad5a26781f3c0ec426fb897; affected: 705d0bf83dbef34d49927d3bf05c6d497f42e8b0 to < 49e05c8d3d8f546a9723e0fca20df02703f9015d; affected: 705d0bf83dbef34d49927d3bf05c6d497f42e8b0 to < 6609261ccf32e95b67b7c762ff23ddd7788114d2; affected: 705d0bf83dbef34d49927d3bf05c6d497f42e8b0 to < 81394dfb9a7905472957628b560ae894eae3a30fSee vendor advisory
LinuxLinuxaffected: 3.18; unaffected: 0 to < 3.18; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ *See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-19 21:16 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed