From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2025-71300: Revert "arm64: zynqmp: Add an OP-TEE node to the device tree"
Date: Fri, 8 May 2026 15:15:25 +0200 [thread overview]
Message-ID: <2026050824-CVE-2025-71300-fe93@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
Revert "arm64: zynqmp: Add an OP-TEE node to the device tree"
This reverts commit 06d22ed6b6635b17551f386b50bb5aaff9b75fbe.
OP-TEE logic in U-Boot automatically injects a reserved-memory
node along with optee firmware node to kernel device tree.
The injection logic is dependent on that there is no manually
defined optee node. Having the node in zynqmp.dtsi effectively
breaks OP-TEE's insertion of the reserved-memory node, causing
memory access violations during runtime.
The Linux kernel CVE team has assigned CVE-2025-71300 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.9 with commit 06d22ed6b6635b17551f386b50bb5aaff9b75fbe and fixed in 6.12.75 with commit eece81eeda10eb42c687399fb5aa69977ae15664
Issue introduced in 6.9 with commit 06d22ed6b6635b17551f386b50bb5aaff9b75fbe and fixed in 6.18.16 with commit 3983ef126e439900bbf419724a9759863c146660
Issue introduced in 6.9 with commit 06d22ed6b6635b17551f386b50bb5aaff9b75fbe and fixed in 6.19.6 with commit 2a833c730d4e8d1cc10953270ce0f3a156145d81
Issue introduced in 6.9 with commit 06d22ed6b6635b17551f386b50bb5aaff9b75fbe and fixed in 7.0 with commit c197179990124f991fca220d97fac56779a02c6d
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-2025-71300
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:
arch/arm64/boot/dts/xilinx/zynqmp.dtsi
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/eece81eeda10eb42c687399fb5aa69977ae15664
https://git.kernel.org/stable/c/3983ef126e439900bbf419724a9759863c146660
https://git.kernel.org/stable/c/2a833c730d4e8d1cc10953270ce0f3a156145d81
https://git.kernel.org/stable/c/c197179990124f991fca220d97fac56779a02c6d
reply other threads:[~2026-05-08 13:15 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=2026050824-CVE-2025-71300-fe93@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@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