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
Security readout for executives and security teams
Plain-English summary
CVE-2022-49235 is a Linux kernel driver bug in ath9k_htc, used for some Atheros USB wireless devices. Missing initialization could send unintended kernel data into USB handling and is scored as mainly an availability risk. It is not listed as actively exploited in the provided sources.
Executive priority
Treat this as routine-to-important kernel maintenance, not an emergency internet-exposed issue. Prioritize shared Linux endpoints, lab systems, and devices using USB wireless adapters. Patch through normal kernel update channels, especially where local users or untrusted workloads exist.
Technical view
Syzbot/KMSAN found uninitialized fields in htc_connect_service() and htc_issue_send() within drivers/net/wireless/ath/ath9k/htc_hst.c. Fixes initialize svc_meta_len and zero the htc_frame_hdr control array. The CVSS vector is local, low complexity, low privilege, no user interaction, high availability impact.
Likely exposure
Exposure is most likely on Linux systems running affected kernel versions where ath9k_htc code is present and exercised, commonly with compatible USB wireless hardware. Systems without this driver, hardware path, or affected kernels are less likely exposed. The source bundle does not identify specific distributions or appliances.
Exploitation context
The provided data marks KEV as false and gives no evidence of active exploitation. CVSS indicates local access with low privileges is required, with no user interaction. The public source describes sanitizer-detected uninitialized memory behavior, not a confirmed public exploit chain.
Researcher notes
The evidence is limited to Linux kernel CVE metadata and stable commits. The description references KMSAN kernel-usb-infoleak reports, while the CVSS vector records no confidentiality or integrity impact and high availability impact. Validate exposure by driver reachability and distribution backport status.
Mitigation direction
Update to a Linux kernel containing the referenced stable ath9k_htc fixes.
Check vendor or distribution advisories for backported kernel packages.
Disable or avoid loading ath9k_htc where the driver is unnecessary.
Prioritize systems using compatible USB wireless hardware or exposed local multi-user environments.
Validation and detection
Inventory Linux kernel versions against the affected and fixed versions in vendor advisories.
Check whether ath9k_htc is built, loaded, or needed on target systems.
Confirm patched source includes initialization of svc_meta_len and htc_frame_hdr control.
Review kernel package changelogs for CVE-2022-49235 or the referenced commit IDs.
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.
cwe · low confidence lookup
CWE-908: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-908 · source CWE mapping
Use of Uninitialized Resource
Use of Uninitialized Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.