[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024110748-CVE-2024-50167-c275@gregkh>
Date: Thu, 7 Nov 2024 10:35:07 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-50167: be2net: fix potential memory leak in be_xmit()
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
be2net: fix potential memory leak in be_xmit()
The be_xmit() returns NETDEV_TX_OK without freeing skb
in case of be_xmit_enqueue() fails, add dev_kfree_skb_any() to fix it.
The Linux kernel CVE team has assigned CVE-2024-50167 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.2 with commit 760c295e0e8d and fixed in 5.15.170 with commit 919ab6e23702
Issue introduced in 4.2 with commit 760c295e0e8d and fixed in 6.1.115 with commit 4c5f170ef4f8
Issue introduced in 4.2 with commit 760c295e0e8d and fixed in 6.6.59 with commit 641c1beed52b
Issue introduced in 4.2 with commit 760c295e0e8d and fixed in 6.11.6 with commit e86a79b804e2
Issue introduced in 4.2 with commit 760c295e0e8d and fixed in 6.12-rc5 with commit e4dd8bfe0f6a
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-2024-50167
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/emulex/benet/be_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/919ab6e2370289a2748780f44a43333cd3878aa7
https://git.kernel.org/stable/c/4c5f170ef4f85731a4d43ad9a6ac51106c0946be
https://git.kernel.org/stable/c/641c1beed52bf3c6deb0193fe4d38ec9ff75d2ae
https://git.kernel.org/stable/c/e86a79b804e26e3b7f1e415b22a085c0bb7ea3d3
https://git.kernel.org/stable/c/e4dd8bfe0f6a23acd305f9b892c00899089bd621
Powered by blists - more mailing lists