Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2022-49235

5.5 · MEDIUM

In the Linux kernel, the following vulnerability has been resolved: ath9k_htc: fix uninit value bugs Syzbot reported 2 KMSAN bugs in ath9k.

Published Feb 26, 2025CWE-908EPSS 0.28%

Overview

CVE-2022-49235 is a medium-severity vulnerability. It was published on February 26, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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:27

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/0b700f7d06492de34964b6f414120043364f8191Refgit.kernel.org/stable/c/11f11ac281f0c0b363d2940204f28bae0422ed71Refgit.kernel.org/stable/c/4d244b731188e0b63fc40a9d2dec72e9181fb37cRefgit.kernel.org/stable/c/5abf2b761b998063f5e2bae93fd4ab10e2a80f10Refgit.kernel.org/stable/c/5c2a6a8daa17a3f65b38b9a5574bb362c13fa1d9Refgit.kernel.org/stable/c/7da6169b6ebb75816b57be3beb829afa74f3b4b6Refgit.kernel.org/stable/c/d1e0df1c57bd30871dd1c855742a7c346dbca853Refgit.kernel.org/stable/c/e352acdd378e9263cc4c6018e588f2dac7161d07Refgit.kernel.org/stable/c/ee4222052a76559c20e821bc3519cefb58b6d3e9

How CyberStrike helps

Frequently asked questions

What is CVE-2022-49235?

CVE-2022-49235 is a medium-severity vulnerability. It was published on February 26, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2022-49235?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2022-49235?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-49235?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-49235 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2022

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999