[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091852-CVE-2022-50387-cd0d@gregkh>
Date: Thu, 18 Sep 2025 15:34:01 +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-50387: net: hinic: fix the issue of CMDQ memory leaks
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net: hinic: fix the issue of CMDQ memory leaks
When hinic_set_cmdq_depth() fails in hinic_init_cmdqs(), the cmdq memory is
not released correctly. Fix it.
The Linux kernel CVE team has assigned CVE-2022-50387 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.8 with commit 72ef908bb3ff9261dc38d079ef332c91418f8693 and fixed in 5.10.153 with commit 6603843c80b16957f5d7d14d897faf13cef2b8b9
Issue introduced in 5.8 with commit 72ef908bb3ff9261dc38d079ef332c91418f8693 and fixed in 5.15.77 with commit 6016d96a6adf66d61655d85da02e1a4c1deccbd6
Issue introduced in 5.8 with commit 72ef908bb3ff9261dc38d079ef332c91418f8693 and fixed in 6.0.7 with commit 9145d512ddff76df88832b29575488199df544a1
Issue introduced in 5.8 with commit 72ef908bb3ff9261dc38d079ef332c91418f8693 and fixed in 6.1 with commit 363cc87767f6ddcfb9158ad2e2afa2f8d5c4b94e
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-50387
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/huawei/hinic/hinic_hw_cmdq.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/6603843c80b16957f5d7d14d897faf13cef2b8b9
https://git.kernel.org/stable/c/6016d96a6adf66d61655d85da02e1a4c1deccbd6
https://git.kernel.org/stable/c/9145d512ddff76df88832b29575488199df544a1
https://git.kernel.org/stable/c/363cc87767f6ddcfb9158ad2e2afa2f8d5c4b94e
Powered by blists - more mailing lists