[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091855-CVE-2022-50418-deac@gregkh>
Date: Thu, 18 Sep 2025 18:04:08 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50418: wifi: ath11k: mhi: fix potential memory leak in ath11k_mhi_register()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
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.
The Linux kernel CVE team has assigned CVE-2022-50418 to this issue.
Affected and fixed versions
===========================
Fixed in 5.19.17 with commit 72ef896e80b6ec7cdc1dd42577045f8e7c9c32b3
Fixed in 6.0.3 with commit 015ced9eb63b8b19cb725a1d592d150b60494ced
Fixed in 6.1 with commit 43e7c3505ec70db3d3c6458824d5fa40f62e3e7b
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2022-50418
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/net/wireless/ath/ath11k/mhi.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/72ef896e80b6ec7cdc1dd42577045f8e7c9c32b3
https://git.kernel.org/stable/c/015ced9eb63b8b19cb725a1d592d150b60494ced
https://git.kernel.org/stable/c/43e7c3505ec70db3d3c6458824d5fa40f62e3e7b
Powered by blists - more mailing lists