Answer in brief
CVE-2022-50418 records a Unknown severity vulnerability in wifi: ath11k: mhi: fix potential memory leak in ath11k_mhi_register(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=6ac04bdc5edb418787ab2040b1f922c23464c750 <72ef896e80b6ec7cdc1dd42577045f8e7c9c32b3 || >=6ac04bdc5edb418787ab2040b1f922c23464c750 <015ced9eb63b8b19cb725a1d592d150b60494ced || >=6ac04bdc5edb418787ab2040b1f922c23464c750 <43e7c3505ec70db3d3c6458824d5fa40f62e3e7b | 72ef896e80b6ec7cdc1dd42577045f8e7c9c32b3, 015ced9eb63b8b19cb725a1d592d150b60494ced, 43e7c3505ec70db3d3c6458824d5fa40f62e3e7b |
| Linux/Linuxgeneric | 5.17 | Not reported |
Published upstream
Sep 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: mhi: fix potential memory leak in ath11k_mhi_register() mhi_alloc_controller() allocates a memory space for mhi_ctrl. When gets some error, mhi_ctrl should be freed with mhi_free_controller(). But when ath11k_mhi_read_addr_from_dt() fails, the function returns without calling mhi_free_controller(), which will lead to a memory leak. We can fix it by calling mhi_free_controller() when ath11k_mhi_read_addr_from_dt() fails.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2022-50418 records a Unknown severity vulnerability in wifi: ath11k: mhi: fix potential memory leak in ath11k_mhi_register(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=6ac04bdc5edb418787ab2040b1f922c23464c750 <72ef896e80b6ec7cdc1dd42577045f8e7c9c32b3 || >=6ac04bdc5edb418787ab2040b1f922c23464c750 <015ced9eb63b8b19cb725a1d592d150b60494ced || >=6ac04bdc5edb418787ab2040b1f922c23464c750 <43e7c3505ec70db3d3c6458824d5fa40f62e3e7b | 72ef896e80b6ec7cdc1dd42577045f8e7c9c32b3, 015ced9eb63b8b19cb725a1d592d150b60494ced, 43e7c3505ec70db3d3c6458824d5fa40f62e3e7b |
| Linux/Linuxgeneric | 5.17 | Not reported |
Published upstream
Sep 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: mhi: fix potential memory leak in ath11k_mhi_register() mhi_alloc_controller() allocates a memory space for mhi_ctrl. When gets some error, mhi_ctrl should be freed with mhi_free_controller(). But when ath11k_mhi_read_addr_from_dt() fails, the function returns without calling mhi_free_controller(), which will lead to a memory leak. We can fix it by calling mhi_free_controller() when ath11k_mhi_read_addr_from_dt() fails.
Quoted source text, attributed separately from HOL analysis.