Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-50179

ath9k: fix use-after-free in ath9k_hif_usb_rx_cb

High7.8EPSS 0.26%
Published
Updated
Reserved
Assigned by
Linux

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]

Scores

CVSS scores of CVE-2022-50179, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.26% · top 82% of all CVEs (6 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Weakness

Affected products

  • Linux · Linux

    • affected fb9987d0f748c983bb795a86f47522313f701a08 – < 62bc1ea5c7401d77eaf73d0c6a15f3d2e742856e
    • affected fb9987d0f748c983bb795a86f47522313f701a08 – < ab7a0ddf5f1cdec63cb21840369873806fc36d80
    • affected fb9987d0f748c983bb795a86f47522313f701a08 – < e9e21206b8ea62220b486310c61277e7ebfe7cec
    • affected fb9987d0f748c983bb795a86f47522313f701a08 – < eccd7c3e2596b574241a7670b5b53f5322f470e5
    • affected fb9987d0f748c983bb795a86f47522313f701a08 – < 03ca957c5f7b55660957eda20b5db4110319ac7a
    • affected fb9987d0f748c983bb795a86f47522313f701a08 – < 6b14ab47937ba441e75e8dbb9fbfc9c55efa41c6
    • affected fb9987d0f748c983bb795a86f47522313f701a08 – < b66ebac40f64336ae2d053883bee85261060bd27
    • affected fb9987d0f748c983bb795a86f47522313f701a08 – < 0ac4827f78c7ffe8eef074bc010e7e34bc22f533
  • Linux · Linux

    • affected 2.6.35
    • unaffected < 2.6.35
    • unaffected 4.14.291 – ≤ 4.14.*
    • unaffected 4.19.256 – ≤ 4.19.*
    • unaffected 5.4.211 – ≤ 5.4.*
    • unaffected 5.10.137 – ≤ 5.10.*
    • unaffected 5.15.61 – ≤ 5.15.*
    • unaffected 5.18.18 – ≤ 5.18.*
    • unaffected 5.19.2 – ≤ 5.19.*
    • unaffected 6.0 – ≤ *

References (8)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50179 badge
[![CVE-2022-50179](https://trackcve.app/badge/CVE-2022-50179.svg)](https://trackcve.app/cve/CVE-2022-50179)

Record last updated .