LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26897: wifi: ath9k: delay all of ath9k_wmi_event_tasklet() until init is complete

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()).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel Wi-Fi driver initialization race in ath9k_htc. A USB wireless device can be exposed before the driver is fully initialized, letting an internal event handler run too early. The public record does not provide CVSS or business-impact scoring, but the most likely concern is local system instability on devices using this driver.

Executive priority

Moderate operational priority where Linux endpoints, appliances, or industrial systems use USB Atheros Wi-Fi. Lower priority for environments without ath9k_htc exposure. Because severity and exploitation evidence are incomplete, handle through normal kernel patch governance, with faster action for exposed devices.

Technical view

ath9k_wmi_event_tasklet() in ath9k_htc assumed driver structures were initialized before processing WMI events. The fix delays the whole tasklet until ath9k_htc_probe_device() completes, extending an earlier partial fix that only handled WMI_TXSTATUS_EVENTID. syzbot reportedly triggered another command path in the race.

Likely exposure

Exposure appears limited to Linux systems that include and use the ath9k_htc USB Atheros wireless driver on affected kernel builds. Traditional servers are less likely exposed unless this driver is present and reachable. Embedded, workstation, and industrial Linux deployments with USB Wi-Fi deserve review.

Exploitation context

The bundle reports syzbot triggered the race, but KEV is false and no provided source states active exploitation in the wild. The record does not show exploit availability, attack preconditions, or remote exploitability. Treat exploitation evidence as incomplete.

Researcher notes

The key behavior is an initialization-order race: USB exposure precedes complete ath9k driver setup, while the WMI event tasklet can dereference not-yet-ready structures. The final fix moves the initialization-complete gate to cover the entire tasklet. Public evidence does not include CVSS, CWE, or confirmed exploit status.

Mitigation direction

  • Apply vendor kernel updates containing the referenced stable fixes.
  • Check Debian LTS, Siemens, or your Linux vendor advisory for packaged fixes.
  • Prioritize systems using ath9k_htc USB Atheros wireless adapters.
  • If updates are unavailable, seek vendor guidance before applying operational workarounds.
  • Track kernel versions against the fixed stable commits listed in the CVE record.

Validation and detection

  • Inventory Linux assets for loaded or packaged ath9k_htc support.
  • Identify devices using USB Atheros ath9k_htc Wi-Fi hardware.
  • Compare running kernel versions with vendor fixed package versions.
  • Review crash logs for ath9k_htc or WMI event tasklet failures.
  • Confirm patched kernels include one of the referenced stable commits.
Prepared
Confidence
medium
Sources
11

Public sources used

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-26897 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
3ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux78c8397132dd4735ac6a7b5a651302f0b9f264ad, 735aefae7b68025cd04c482a940c0f6fc6797a63, 8b3046abc99eefe11438090bcc4ec3a3994b55d0, 8b3046abc99eefe11438090bcc4ec3a3994b55d0, 8b3046abc99eefe11438090bcc4ec3a3994b55d0, 8b3046abc99eefe11438090bcc4ec3a3994b55d0, 8b3046abc99eefe11438090bcc4ec3a3994b55d0, 7bbc1a50a7963f14048f0e54b0b73159f86d4ea3, 5.10.136, 5.15.17, 5.16.3unaffected
LinuxLinux5.17, 0, 5.10.214, 5.15.153, 6.1.83, 6.6.23, 6.7.11, 6.8.2, 6.9affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.