LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50179: ath9k: fix use-after-free in ath9k_hif_usb_rx_cb

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]

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-50179 is a Linux kernel driver flaw in ath9k USB wireless handling. A failed device probe can leave later interrupt-driven receive processing touching freed memory. Business urgency depends on whether affected kernels use this wireless driver or hardware.

Executive priority

Treat as a targeted kernel-maintenance issue, not a broad emergency. Prioritize affected Linux assets using the relevant wireless driver, especially managed endpoints or appliances where kernel crashes affect availability.

Technical view

The issue is a use-after-free in ath9k_hif_usb_rx_cb(). During ath9k_htc_probe_device(), htc_handle->drv_priv could be initialized before ath9k_htc_wait_for_target() fails and ieee80211_free_hw() frees priv, then RX statistics access can dereference stale drv_priv.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the ath9k HTC USB wireless path present and reachable. Systems without the affected driver or hardware are less likely exposed, but the bundle does not provide complete distro package mappings.

Exploitation context

The source bundle cites syzbot findings and kernel fixes. It does not cite active exploitation, KEV listing, exploit availability, CVSS, or a confirmed real-world attack path.

Researcher notes

The fix moves drv_priv initialization later in probe flow and makes related statistics macros NULL-safe. The evidence supports a memory-safety bug found by syzbot, but impact, privilege boundary, and exploitability are not characterized in the bundle.

Mitigation direction

  • Apply a Linux kernel update that includes the referenced stable fixes.
  • Check your Linux distribution or vendor advisory for backported fixed kernel versions.
  • Prioritize systems using USB Atheros ath9k HTC wireless devices or modules.
  • Track kernel inventory against affected and fixed versions before deployment.
  • Avoid claiming remediation complete until vendor backport status is confirmed.

Validation and detection

  • Inventory Linux kernel versions across endpoints, appliances, and embedded systems.
  • Check whether ath9k HTC USB wireless support is built, loaded, or required.
  • Confirm the running kernel includes the relevant stable fix or vendor backport.
  • Review kernel crash telemetry for ath9k_hif_usb_rx_cb or ath9k_htc probe failures.
  • Document systems where exposure cannot be determined from available inventory.
Prepared
Confidence
medium
Sources
10

Public sources used

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.

cve · low confidence lookup

CVE-2022-50179 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxfb9987d0f748c983bb795a86f47522313f701a08, fb9987d0f748c983bb795a86f47522313f701a08, fb9987d0f748c983bb795a86f47522313f701a08, fb9987d0f748c983bb795a86f47522313f701a08, fb9987d0f748c983bb795a86f47522313f701a08, fb9987d0f748c983bb795a86f47522313f701a08, fb9987d0f748c983bb795a86f47522313f701a08, fb9987d0f748c983bb795a86f47522313f701a08unaffected
LinuxLinux2.6.35, 0, 4.14.291, 4.19.256, 5.4.211, 5.10.137, 5.15.61, 5.18.18, 5.19.2, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.