[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025120943-CVE-2022-50663-5606@gregkh>
Date: Tue, 9 Dec 2025 10:30:48 +0900
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50663: net: stmmac: fix possible memory leak in stmmac_dvr_probe()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net: stmmac: fix possible memory leak in stmmac_dvr_probe()
The bitmap_free() should be called to free priv->af_xdp_zc_qps
when create_singlethread_workqueue() fails, otherwise there will
be a memory leak, so we add the err path error_wq_init to fix it.
The Linux kernel CVE team has assigned CVE-2022-50663 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.13 with commit bba2556efad66e7eaa56fece13f7708caa1187f8 and fixed in 5.15.86 with commit 96e50897029f65222ef76cfe9bc802321fcea33b
Issue introduced in 5.13 with commit bba2556efad66e7eaa56fece13f7708caa1187f8 and fixed in 6.0.16 with commit b59253e32c203a20bce15dca80890b7d268bacd7
Issue introduced in 5.13 with commit bba2556efad66e7eaa56fece13f7708caa1187f8 and fixed in 6.1.2 with commit 446757787baf99b7db15cb347783c45a37bfe21f
Issue introduced in 5.13 with commit bba2556efad66e7eaa56fece13f7708caa1187f8 and fixed in 6.2 with commit a137f3f27f9290933fe7e40e6dc8a445781c31a2
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-50663
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/stmicro/stmmac/stmmac_main.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/96e50897029f65222ef76cfe9bc802321fcea33b
https://git.kernel.org/stable/c/b59253e32c203a20bce15dca80890b7d268bacd7
https://git.kernel.org/stable/c/446757787baf99b7db15cb347783c45a37bfe21f
https://git.kernel.org/stable/c/a137f3f27f9290933fe7e40e6dc8a445781c31a2
Powered by blists - more mailing lists