[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024110807-CVE-2024-50209-d763@gregkh>
Date: Fri, 8 Nov 2024 07:08:10 +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-50209: RDMA/bnxt_re: Add a check for memory allocation
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
RDMA/bnxt_re: Add a check for memory allocation
__alloc_pbl() can return error when memory allocation fails.
Driver is not checking the status on one of the instances.
The Linux kernel CVE team has assigned CVE-2024-50209 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.7 with commit 0c4dcd602817 and fixed in 5.15.170 with commit 322a19baaaa2
Issue introduced in 5.7 with commit 0c4dcd602817 and fixed in 6.1.115 with commit 76dd679c3b14
Issue introduced in 5.7 with commit 0c4dcd602817 and fixed in 6.6.59 with commit c71957271f2e
Issue introduced in 5.7 with commit 0c4dcd602817 and fixed in 6.11.6 with commit ba9045887b43
Issue introduced in 5.7 with commit 0c4dcd602817 and fixed in 6.12-rc4 with commit c5c1ae73b774
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-50209
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/infiniband/hw/bnxt_re/qplib_res.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/322a19baaaa25a1fe8ce9fceaed9409ad847844c
https://git.kernel.org/stable/c/76dd679c3b148d23f72dcf6c3cde3d5f746b2c07
https://git.kernel.org/stable/c/c71957271f2e8133a6aa82001c2fa671d5008129
https://git.kernel.org/stable/c/ba9045887b435a4c5551245ae034b8791b4e4aaa
https://git.kernel.org/stable/c/c5c1ae73b7741fa3b58e6e001b407825bb971225
Powered by blists - more mailing lists