Skip to main content

CVE-2022-49235: Vulnerability in Linux Linux

Medium
VulnerabilityCVE-2022-49235cvecve-2022-49235
Published: Wed Feb 26 2025 (02/26/2025, 01:56:00 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: ath9k_htc: fix uninit value bugs Syzbot reported 2 KMSAN bugs in ath9k. All of them are caused by missing field initialization. In htc_connect_service() svc_meta_len and pad are not initialized. Based on code it looks like in current skb there is no service data, so simply initialize svc_meta_len to 0. htc_issue_send() does not initialize htc_frame_hdr::control array. Based on firmware code, it will initialize it by itself, so simply zero whole array to make KMSAN happy Fail logs: BUG: KMSAN: kernel-usb-infoleak in usb_submit_urb+0x6c1/0x2aa0 drivers/usb/core/urb.c:430 usb_submit_urb+0x6c1/0x2aa0 drivers/usb/core/urb.c:430 hif_usb_send_regout drivers/net/wireless/ath/ath9k/hif_usb.c:127 [inline] hif_usb_send+0x5f0/0x16f0 drivers/net/wireless/ath/ath9k/hif_usb.c:479 htc_issue_send drivers/net/wireless/ath/ath9k/htc_hst.c:34 [inline] htc_connect_service+0x143e/0x1960 drivers/net/wireless/ath/ath9k/htc_hst.c:275 ... Uninit was created at: slab_post_alloc_hook mm/slab.h:524 [inline] slab_alloc_node mm/slub.c:3251 [inline] __kmalloc_node_track_caller+0xe0c/0x1510 mm/slub.c:4974 kmalloc_reserve net/core/skbuff.c:354 [inline] __alloc_skb+0x545/0xf90 net/core/skbuff.c:426 alloc_skb include/linux/skbuff.h:1126 [inline] htc_connect_service+0x1029/0x1960 drivers/net/wireless/ath/ath9k/htc_hst.c:258 ... Bytes 4-7 of 18 are uninitialized Memory access of size 18 starts at ffff888027377e00 BUG: KMSAN: kernel-usb-infoleak in usb_submit_urb+0x6c1/0x2aa0 drivers/usb/core/urb.c:430 usb_submit_urb+0x6c1/0x2aa0 drivers/usb/core/urb.c:430 hif_usb_send_regout drivers/net/wireless/ath/ath9k/hif_usb.c:127 [inline] hif_usb_send+0x5f0/0x16f0 drivers/net/wireless/ath/ath9k/hif_usb.c:479 htc_issue_send drivers/net/wireless/ath/ath9k/htc_hst.c:34 [inline] htc_connect_service+0x143e/0x1960 drivers/net/wireless/ath/ath9k/htc_hst.c:275 ... Uninit was created at: slab_post_alloc_hook mm/slab.h:524 [inline] slab_alloc_node mm/slub.c:3251 [inline] __kmalloc_node_track_caller+0xe0c/0x1510 mm/slub.c:4974 kmalloc_reserve net/core/skbuff.c:354 [inline] __alloc_skb+0x545/0xf90 net/core/skbuff.c:426 alloc_skb include/linux/skbuff.h:1126 [inline] htc_connect_service+0x1029/0x1960 drivers/net/wireless/ath/ath9k/htc_hst.c:258 ... Bytes 16-17 of 18 are uninitialized Memory access of size 18 starts at ffff888027377e00

AI-Powered Analysis

AILast updated: 06/30/2025, 04:40:32 UTC

Technical Analysis

CVE-2022-49235 is a vulnerability identified in the Linux kernel specifically affecting the ath9k_htc wireless driver, which handles Atheros 802.11n USB wireless devices. The issue arises from uninitialized memory usage in two functions: htc_connect_service() and htc_issue_send(). In htc_connect_service(), the variables svc_meta_len and pad are not initialized, which can lead to undefined behavior. Similarly, in htc_issue_send(), the control array within the htc_frame_hdr structure is not initialized before use. These uninitialized values can cause kernel memory sanitization (KMSAN) warnings and potentially lead to information leaks or unpredictable kernel behavior. The root cause is missing field initialization in the driver code, which was detected by Syzbot, an automated kernel fuzzing tool. The vulnerability manifests as kernel USB info leaks during usb_submit_urb() calls, as uninitialized memory is accessed and potentially exposed. The flaw is located in the wireless driver code path related to USB communication with the ath9k_htc device. Although the firmware may initialize some fields, the kernel driver does not explicitly zero out these fields, leading to the issue. The vulnerability affects Linux kernel versions identified by the commit hash fb9987d0f748c983bb795a86f47522313f701a08 and potentially others in the same timeframe before the fix. No known exploits are reported in the wild at this time. The vulnerability does not have an assigned CVSS score but is classified as a kernel memory info leak due to uninitialized memory usage, which can impact system stability and confidentiality of kernel memory contents.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to systems using Linux with the ath9k_htc wireless driver, commonly found in devices utilizing Atheros USB Wi-Fi adapters. The impact includes potential kernel memory information leaks, which could allow attackers with local access or the ability to trigger specific USB wireless operations to glean sensitive kernel memory data. This could aid in further exploitation such as privilege escalation or bypassing security mechanisms. While remote exploitation is unlikely without user interaction or local access, environments with shared Linux systems, such as enterprise servers, workstations, or embedded devices using this driver, could be at risk. Confidentiality of kernel memory could be compromised, potentially exposing cryptographic keys or other sensitive information. Additionally, uninitialized memory usage can lead to system instability or crashes, impacting availability. Given the widespread use of Linux in European critical infrastructure, government, and enterprise environments, especially in countries with strong Linux adoption, this vulnerability could affect operational security and data protection compliance if exploited.

Mitigation Recommendations

European organizations should take the following specific mitigation steps: 1) Identify and inventory all Linux systems using the ath9k_htc driver, focusing on devices with Atheros USB wireless adapters. 2) Apply the latest Linux kernel updates that include the patch fixing this vulnerability, ensuring the driver initializes all fields properly. 3) For systems where immediate patching is not feasible, consider disabling the ath9k_htc driver or replacing affected hardware with alternatives not using this driver. 4) Implement strict access controls to limit local user access to trusted personnel only, reducing the risk of exploitation. 5) Monitor kernel logs for KMSAN warnings or unusual usb_submit_urb() activity that may indicate attempts to trigger the vulnerability. 6) Employ kernel hardening techniques such as Kernel Address Space Layout Randomization (KASLR) and secure boot to reduce exploitation likelihood. 7) Educate system administrators about this vulnerability and the importance of timely patching and monitoring.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2025-02-26T01:49:39.294Z
Cisa Enriched
false
Cvss Version
null
State
PUBLISHED

Threat ID: 682d982dc4522896dcbe5392

Added to database: 5/21/2025, 9:09:01 AM

Last enriched: 6/30/2025, 4:40:32 AM

Last updated: 8/14/2025, 3:33:11 PM

Views: 16

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats