[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025122421-CVE-2022-50711-30c0@gregkh>
Date: Wed, 24 Dec 2025 11:56:28 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50711: net: ethernet: mtk_eth_soc: fix possible memory leak in mtk_probe()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net: ethernet: mtk_eth_soc: fix possible memory leak in mtk_probe()
If mtk_wed_add_hw() has been called, mtk_wed_exit() needs be called
in error path or removing module to free the memory allocated in
mtk_wed_add_hw().
The Linux kernel CVE team has assigned CVE-2022-50711 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.19 with commit 804775dfc2885e93a0a4b35db1914c2cc25172b5 and fixed in 6.0.6 with commit 96bde7c4f5683d8c1c809ddb781ef3fdec9b7215
Issue introduced in 5.19 with commit 804775dfc2885e93a0a4b35db1914c2cc25172b5 and fixed in 6.1 with commit b3d0d98179d62f9d55635a600679c4fa362baf8d
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-50711
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/ethernet/mediatek/mtk_eth_soc.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/96bde7c4f5683d8c1c809ddb781ef3fdec9b7215
https://git.kernel.org/stable/c/b3d0d98179d62f9d55635a600679c4fa362baf8d
Powered by blists - more mailing lists