CVE-2022-50740 — wifi: ath9k: hif_usb: fix memory leak of urbs in ath9k_hif_usb_dealloc_tx_urbs()
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.3% (30-day exploitation probability)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version 7f5972267295fe49f8da8eb42bc2eb3d140860c0version 5.10≥ 5.9.2 and < 5.10≥ 5.8.17 and < 5.9≥ 4.4.241 and < 4.5≥ 5.4.73 and < 5.4.229≥ 4.19.154 and < 4.19.270≥ 4.14.203 and < 4.14.303 and 12 more≥ 4.9.241 and < 4.9.337version 2d72d5ce63c92f56b9f978e8befb5838144176b9≥ 6f0706ef39fecc6bf56d67728fe0c94e26b43e9d and < 134ae5eba41294eff76e4be20d6001b8f0192207version b92e116ae36f498858dbb18e29a066c3f5348965≥ 03fb92a432ea5abe5909bca1455b7e44a9380480 and < c2a94de38c74e86f49124ac14f093d6a5c377a90≥ 03fb92a432ea5abe5909bca1455b7e44a9380480 and < 08aa0537ec8cf29ceccae98acc1a534fc12598c1≥ 03fb92a432ea5abe5909bca1455b7e44a9380480 and < c05189a429fdb371dd455c3c466d67ac2ebff152≥ 03fb92a432ea5abe5909bca1455b7e44a9380480 and < d856f7574bcc1d81de565a857caf32f122cd7ce0≥ 03fb92a432ea5abe5909bca1455b7e44a9380480 and < c3fb3e9a2c0c1a0fa492d90eb19bcfa92a5f884d≥ a9990ed2d7ca9339d37c7f67d6f5cb298c3f1b34 and < 9850791d389b342ae6e573fe8198db0b4d338352≥ df4318440c1568b7dedc5f7d4e617d0e297a1313 and < eddbb8f7620f9f8008b090a6e10c460074ca575a≥ 795d57a558d106b8a5bc2bd7aeaf707d9a099244 and < 472312fef2b9eccaa03bd59e0ab2527da945e736 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.28%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Deferred
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
9 on the record
- git.kernel.org/stable/c/d856f7574bcc1d81de565a857caf32f122cd7ce0
- git.kernel.org/stable/c/c2a94de38c74e86f49124ac14f093d6a5c377a90
- git.kernel.org/stable/c/134ae5eba41294eff76e4be20d6001b8f0192207
- git.kernel.org/stable/c/08aa0537ec8cf29ceccae98acc1a534fc12598c1
- git.kernel.org/stable/c/9850791d389b342ae6e573fe8198db0b4d338352
- git.kernel.org/stable/c/eddbb8f7620f9f8008b090a6e10c460074ca575a
- git.kernel.org/stable/c/472312fef2b9eccaa03bd59e0ab2527da945e736
- git.kernel.org/stable/c/c05189a429fdb371dd455c3c466d67ac2ebff152
- git.kernel.org/stable/c/c3fb3e9a2c0c1a0fa492d90eb19bcfa92a5f884d
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 6h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 6h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2022-50740 is "wifi: ath9k: hif_usb: fix memory leak of urbs in ath9k_hif_usb_dealloc_tx_urbs()", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.28% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.