From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-27025: nbd: null check for nla_nest_start
Date: Wed, 1 May 2024 14:50:08 +0200 [thread overview]
Message-ID: <2024050107-CVE-2024-27025-babd@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
nbd: null check for nla_nest_start
nla_nest_start() may fail and return NULL. Insert a check and set errno
based on other call sites within the same source code.
The Linux kernel CVE team has assigned CVE-2024-27025 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.12 with commit 47d902b90a32 and fixed in 5.4.273 with commit 44214d744be3
Issue introduced in 4.12 with commit 47d902b90a32 and fixed in 5.10.214 with commit 4af837db0fd3
Issue introduced in 4.12 with commit 47d902b90a32 and fixed in 5.15.153 with commit 98e60b538e66
Issue introduced in 4.12 with commit 47d902b90a32 and fixed in 6.1.83 with commit 96436365e5d8
Issue introduced in 4.12 with commit 47d902b90a32 and fixed in 6.6.23 with commit b7f5aed55829
Issue introduced in 4.12 with commit 47d902b90a32 and fixed in 6.7.11 with commit e803040b368d
Issue introduced in 4.12 with commit 47d902b90a32 and fixed in 6.8.2 with commit ba6a9970ce9e
Issue introduced in 4.12 with commit 47d902b90a32 and fixed in 6.9-rc1 with commit 31edf4bbe0ba
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-27025
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/block/nbd.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/44214d744be32a4769faebba764510888f1eb19e
https://git.kernel.org/stable/c/4af837db0fd3679fabc7b7758397090b0c06dced
https://git.kernel.org/stable/c/98e60b538e66c90b9a856828c71d4e975ebfa797
https://git.kernel.org/stable/c/96436365e5d80d0106ea785a4f80a58e7c9edff8
https://git.kernel.org/stable/c/b7f5aed55829f376e4f7e5ea5b80ccdcb023e983
https://git.kernel.org/stable/c/e803040b368d046434fbc8a91945c690332c4fcf
https://git.kernel.org/stable/c/ba6a9970ce9e284cbc04099361c58731e308596a
https://git.kernel.org/stable/c/31edf4bbe0ba27fd03ac7d87eb2ee3d2a231af6d
reply other threads:[~2024-05-01 12:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2024050107-CVE-2024-27025-babd@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).