Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2022-50179

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: ath9k: fix use-after-free in ath9k_hif_usb_rx_cb Syzbot reported use-after-free Read in ath9k_hif_usb_rx_cb() [0].

Published Jun 18, 2025CWE-416EPSS 0.25%

Overview

CVE-2022-50179 is a high-severity vulnerability. It was published on June 18, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. 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: fix use-after-free in ath9k_hif_usb_rx_cb

Syzbot reported use-after-free Read in ath9k_hif_usb_rx_cb() [0]. The

problem was in incorrect htc_handle->drv_priv initialization.

Probable call trace which can trigger use-after-free:

ath9k_htc_probe_device()

/* htc_handle->drv_priv = priv; */

ath9k_htc_wait_for_target() <--- Failed

ieee80211_free_hw() <--- priv pointer is freed

<IRQ>

...

ath9k_hif_usb_rx_cb()

ath9k_hif_usb_rx_stream()

RX_STAT_INC() <--- htc_handle->drv_priv access

In order to not add fancy protection for drv_priv we can move

htc_handle->drv_priv initialization at the end of the

ath9k_htc_probe_device() and add helper macro to make

all *_STAT_* macros NULL safe, since syzbot has reported related NULL

deref in that macros [1]

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/03ca957c5f7b55660957eda20b5db4110319ac7aRefgit.kernel.org/stable/c/0ac4827f78c7ffe8eef074bc010e7e34bc22f533Refgit.kernel.org/stable/c/62bc1ea5c7401d77eaf73d0c6a15f3d2e742856eRefgit.kernel.org/stable/c/6b14ab47937ba441e75e8dbb9fbfc9c55efa41c6Refgit.kernel.org/stable/c/ab7a0ddf5f1cdec63cb21840369873806fc36d80Refgit.kernel.org/stable/c/b66ebac40f64336ae2d053883bee85261060bd27Refgit.kernel.org/stable/c/e9e21206b8ea62220b486310c61277e7ebfe7cecRefgit.kernel.org/stable/c/eccd7c3e2596b574241a7670b5b53f5322f470e5

How CyberStrike helps

Frequently asked questions

What is CVE-2022-50179?

CVE-2022-50179 is a high-severity vulnerability. It was published on June 18, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2022-50179?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. 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-50179?

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-50179?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-50179 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 HIGH CVEs from 2022

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999