CVE-2022-50709

published 24 Dec 2025 · updated 12 Nov 2026

wifi: ath9k: avoid uninit memory read in ath9k_htc_rx_msg()

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f3d2a3b7e290d0bdbddfcee5a6c3d922e2b7e02a, Kernel 0d2649b288b7b9484e3d4380c0d6c4720a17e473, Kernel 2c485f4f2a64258acc5228e78ffb828c68d9e770 and 12 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=fb9987d0f748c983bb795a86f47522313f701a08 <f3d2a3b7e290d0bdbddfcee5a6c3d922e2b7e02a, >=fb9987d0f748c983bb795a86f47522313f701a08 <0d2649b288b7b9484e3d4380c0d6c4720a17e473, >=fb9987d0f748c983bb795a86f47522313f701a08 <2c485f4f2a64258acc5228e78ffb828c68d9e770, >=fb9987d0f748c983bb795a86f47522313f701a08 <4891a50f5ed8bfcb8f2a4b816b0676f398687783, >=fb9987d0f748c983bb795a86f47522313f701a08 <84242f15f911f34aec9b22f99d1e9bff19723dbe, >=fb9987d0f748c983bb795a86f47522313f701a08 <9661724f6206bd606ecf13acada676a9975d230b, >=fb9987d0f748c983bb795a86f47522313f701a08 <b1b4144508adfc585e43856b31baaf9008a3beb4, >=fb9987d0f748c983bb795a86f47522313f701a08 <b383e8abed41cc6ff1a3b34de75df9397fa4878c, =2.6.35f3d2a3b7e290d0bdbddfcee5a6c3d922e2b7e02a, 0d2649b288b7b9484e3d4380c0d6c4720a17e473, 2c485f4f2a64258acc5228e78ffb828c68d9e770, 4891a50f5ed8bfcb8f2a4b816b0676f398687783, 84242f15f911f34aec9b22f99d1e9bff19723dbe, 9661724f6206bd606ecf13acada676a9975d230b, b1b4144508adfc585e43856b31baaf9008a3beb4, b383e8abed41cc6ff1a3b34de75df9397fa4878c
linux-kernel: Kernel>=4.15.0 <4.19.262, >=4.20.0 <5.4.220, >=5.11.0 <5.15.75, >=5.16.0 <5.19.17, >=5.20.0 <6.0.3, >=5.5.0 <5.10.150, >=2.6.35 <4.14.2964.19.262, 5.4.220, 5.15.75, 5.19.17, 6.0.3, 5.10.150, 4.14.296

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2022-50709 severity on Zeptric[![CVE-2022-50709](https://zeptric.io/badge/cve/CVE-2022-50709.svg)](https://zeptric.io/cve/CVE-2022-50709)