LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50709: wifi: ath9k: avoid uninit memory read in ath9k_htc_rx_msg()

In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: avoid uninit memory read in ath9k_htc_rx_msg() syzbot is reporting uninit value at ath9k_htc_rx_msg() [1], for ioctl(USB_RAW_IOCTL_EP_WRITE) can call ath9k_hif_usb_rx_stream() with pkt_len = 0 but ath9k_hif_usb_rx_stream() uses __dev_alloc_skb(pkt_len + 32, GFP_ATOMIC) based on an assumption that pkt_len is valid. As a result, ath9k_hif_usb_rx_stream() allocates skb with uninitialized memory and ath9k_htc_rx_msg() is reading from uninitialized memory. Since bytes accessed by ath9k_htc_rx_msg() is not known until ath9k_htc_rx_msg() is called, it would be difficult to check minimal valid pkt_len at "if (pkt_len > 2 * MAX_RX_BUF_SIZE) {" line in ath9k_hif_usb_rx_stream(). We have two choices. One is to workaround by adding __GFP_ZERO so that ath9k_htc_rx_msg() sees 0 if pkt_len is invalid. The other is to let ath9k_htc_rx_msg() validate pkt_len before accessing. This patch chose the latter. Note that I'm not sure threshold condition is correct, for I can't find details on possible packet length used by this protocol.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-50709 is a Linux kernel flaw in the ath9k HTC Wi-Fi USB driver. A malformed receive message can make the kernel read uninitialized memory. Public data does not provide CVSS, impact severity, or evidence of active exploitation.

Executive priority

Treat as a routine-to-prioritized kernel maintenance item unless ath9k HTC USB Wi-Fi is deployed in sensitive environments. There is no sourced evidence of active exploitation, but kernel memory issues deserve timely patch validation.

Technical view

The issue is in ath9k_htc_rx_msg(). syzbot found that USB_RAW_IOCTL_EP_WRITE can reach ath9k_hif_usb_rx_stream() with pkt_len=0, leading to skb allocation containing uninitialized memory and a later uninitialized read. The fix validates pkt_len before access.

Likely exposure

Systems running affected Linux kernel versions with the ath9k_htc/ath9k HTC USB Wi-Fi driver are the most relevant exposure. The CVE record lists Linux kernel versions from 2.6.35 through fixed stable releases as affected, but distribution backport status must be verified separately.

Exploitation context

The public record describes syzbot discovery and a kernel-side trigger path involving USB_RAW_IOCTL_EP_WRITE. CISA KEV is false in the provided data, and no cited source states active exploitation. Required privileges, reachability, and real-world exploitability are not fully established in the sources.

Researcher notes

The CVE source notes uncertainty about the exact packet-length threshold for the protocol. Analysis should focus on the fixed validation logic and affected stable branches. Avoid assuming broader Wi-Fi stack exposure beyond ath9k HTC USB handling shown in the references.

Mitigation direction

  • Apply kernel updates containing the referenced stable fixes.
  • Check your Linux distribution’s advisory for backported fixes.
  • Disable or avoid loading ath9k_htc where it is not required.
  • Prioritize systems using Atheros HTC USB Wi-Fi hardware.

Validation and detection

  • Inventory Linux kernel versions across endpoints and appliances.
  • Check whether ath9k_htc is present or loaded.
  • Compare installed kernel builds against vendor fixed packages.
  • Confirm the relevant stable patch is included in source or changelog.
  • Document exceptions where the driver or hardware is absent.
Prepared
Confidence
medium
Sources
10

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-2022-50709 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
0ADP providers
9Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxfb9987d0f748c983bb795a86f47522313f701a08, fb9987d0f748c983bb795a86f47522313f701a08, fb9987d0f748c983bb795a86f47522313f701a08, fb9987d0f748c983bb795a86f47522313f701a08, fb9987d0f748c983bb795a86f47522313f701a08, fb9987d0f748c983bb795a86f47522313f701a08, fb9987d0f748c983bb795a86f47522313f701a08, fb9987d0f748c983bb795a86f47522313f701a08unaffected
LinuxLinux2.6.35, 0, 4.14.296, 4.19.262, 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3, 6.1affected
Weakness

CWE details

No CWE listed

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