From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2021-47134: efi/fdt: fix panic when no valid fdt found
Date: Fri, 15 Mar 2024 21:15:24 +0100 [thread overview]
Message-ID: <2024031515-CVE-2021-47134-3348@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
efi/fdt: fix panic when no valid fdt found
setup_arch() would invoke efi_init()->efi_get_fdt_params(). If no
valid fdt found then initial_boot_params will be null. So we
should stop further fdt processing here. I encountered this
issue on risc-v.
The Linux kernel CVE team has assigned CVE-2021-47134 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.10 with commit b91540d52a08b and fixed in 5.10.43 with commit 5148066edbdc
Issue introduced in 5.10 with commit b91540d52a08b and fixed in 5.12.10 with commit 8a7e8b4e5631
Issue introduced in 5.10 with commit b91540d52a08b and fixed in 5.13 with commit 668a84c1bfb2
Please see https://www.kernel.org or 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-2021-47134
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/firmware/efi/fdtparams.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/5148066edbdc89c6fe5bc419c31a5c22e5f83bdb
https://git.kernel.org/stable/c/8a7e8b4e5631a03ea2fee27957857a56612108ca
https://git.kernel.org/stable/c/668a84c1bfb2b3fd5a10847825a854d63fac7baa
reply other threads:[~2024-03-15 20:16 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=2024031515-CVE-2021-47134-3348@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).