CVE-2022-50740

wifi: ath9k: hif_usb: fix memory leak of urbs in ath9k_hif_usb_dealloc_tx_urbs()

N/A
Published: December 24, 2025 at 01:05 PM UTC
Updated: June 17, 2026 at 05:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.3%

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: hif_usb: fix memory leak of urbs in ath9k_hif_usb_dealloc_tx_urbs() Syzkaller reports a long-known leak of urbs in ath9k_hif_usb_dealloc_tx_urbs(). The cause of the leak is that usb_get_urb() is called but usb_free_urb() (or usb_put_urb()) is not called inside usb_kill_urb() as urb->dev or urb->ep fields have not been initialized and usb_kill_urb() returns immediately. The patch removes trying to kill urbs located in hif_dev->tx.tx_buf because hif_dev->tx.tx_buf is not supposed to contain urbs which are in pending state (the pending urbs are stored in hif_dev->tx.tx_pending). The tx.tx_lock is acquired so there should not be any changes in the list. Found by Linux Verification Center (linuxtesting.org) with Syzkaller.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 4.4.241v ≥ 5.8.17v ≥ 5.9.24.14.203 ≤ v < 4.14.3034.19.154 ≤ v < 4.19.2704.4.241 ≤ v < 4.54.9.241 ≤ v < 4.9.3375.10 ≤ v < 5.10.1635.10 ≤ v < 5.15.865.10 ≤ v < 6.0.165.10 ≤ v < 6.1.25.10 ≤ v < 6.25.4.73 ≤ v < 5.4.2295.8.17 ≤ v < 5.95.9.2 ≤ v < 5.102d72d5ce63c92f56b9f978e8befb5838144176b93fb92a432ea5abe5909bca1455b7e44a93804804.14.2034.19.1544.4.2414.9.2415.105.4.735.8.175.9.26f0706ef39fecc6bf56d67728fe0c94e26b43e9d795d57a558d106b8a5bc2bd7aeaf707d9a0992447f5972267295fe49f8da8eb42bc2eb3d140860c0a9990ed2d7ca9339d37c7f67d6f5cb298c3f1b34b92e116ae36f498858dbb18e29a066c3f5348965df4318440c1568b7dedc5f7d4e617d0e297a1313
Vendor states this is fixed in 08aa0537ec8cf29ceccae98acc1a534fc12598c1 (fixed)
Vendor states this is fixed in 134ae5eba41294eff76e4be20d6001b8f0192207 (fixed)
Vendor states this is fixed in 472312fef2b9eccaa03bd59e0ab2527da945e736 (fixed)
Vendor states this is fixed in 9850791d389b342ae6e573fe8198db0b4d338352 (fixed)
Vendor states this is fixed in c05189a429fdb371dd455c3c466d67ac2ebff152 (fixed)
Vendor states this is fixed in c2a94de38c74e86f49124ac14f093d6a5c377a90 (fixed)
Vendor states this is fixed in c3fb3e9a2c0c1a0fa492d90eb19bcfa92a5f884d (fixed)
Vendor states this is fixed in d856f7574bcc1d81de565a857caf32f122cd7ce0 (fixed)
Vendor states this is fixed in eddbb8f7620f9f8008b090a6e10c460074ca575a (fixed)
Vendor states this is fixed in 4.14.303 (unaffected)
Vendor states this is fixed in 4.19.270 (unaffected)
Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.9.337 (unaffected)
Vendor states this is fixed in 5.10 (unaffected)
Vendor states this is fixed in 5.10.163 (unaffected)
Vendor states this is fixed in 5.15.86 (unaffected)
Vendor states this is fixed in 5.4.229 (unaffected)
Affected range stops below 5.9, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.0.16 (unaffected)
Vendor states this is fixed in 6.1.2 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (9)

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card