Security readout for executives and security teams
Plain-English summary
A Linux device-tree conflict on ARM64 ZynqMP systems can prevent U-Boot from reserving memory correctly for OP-TEE. The resulting runtime memory access violations may compromise confidentiality, integrity, or availability. This is primarily relevant to embedded systems using this specific hardware and trusted-execution configuration, not general Linux deployments.
Executive priority
Prioritize affected ZynqMP embedded systems, especially production, safety-sensitive, or high-trust workloads. General Linux fleets are unlikely to share the required platform configuration. Treat confirmed exposure as high priority because runtime memory violations can affect all three security objectives, while recognizing that active exploitation is not established.
Technical view
The manually defined OP-TEE node introduced by commit 06d22ed6b663 prevents U-Boot’s OP-TEE logic from injecting its required reserved-memory node. Without that reservation, runtime components may access overlapping or invalid memory. The stable-kernel resolution reverts the conflicting device-tree change. CVSS 3.1 rates local, low-complexity, low-privilege impact at 7.8.
Likely exposure
Exposure requires ARM64 Xilinx ZynqMP hardware using OP-TEE with U-Boot’s automatic device-tree injection and a kernel containing the conflicting change. The bundle lists several affected releases, but its version representation is ambiguous; confirm exact branches through commit ancestry and distributor advisories.
Exploitation context
The CVSS vector describes local access with low privileges, no user interaction, and potentially high confidentiality, integrity, and availability impact. The supplied record is not in KEV, and no source provided reports active exploitation or a public exploit. Memory violations may also arise operationally without deliberate exploitation.
Researcher notes
The root cause is device-tree ownership conflict between the kernel source and U-Boot’s conditional OP-TEE injection. Analysis should compare the compiled and effective boot-time trees, because U-Boot mutates the tree before kernel startup. The supplied references identify four stable fixes, but the bundle does not map each commit to a release branch or clarify the duplicated version entries.
Mitigation direction
- Apply a supported stable-kernel update containing the appropriate referenced revert.
- Confirm the selected update matches the deployed kernel branch and vendor build.
- Consult the kernel or device vendor if no validated update is available.
- Avoid unsupported device-tree modifications unless explicitly validated by the platform vendor.
Validation and detection
- Inventory ARM64 ZynqMP systems using OP-TEE and U-Boot device-tree injection.
- Check whether deployed kernel source contains commit 06d22ed6b663 or its backport.
- Verify the applicable stable revert is present in each deployed kernel build.
- Inspect the effective boot-time device tree for OP-TEE reserved-memory reservation.
- Test OP-TEE workloads for memory violations after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2025-71300 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/eece81eeda10eb42c687399fb5aa69977ae15664CVE reference, Linux
- https://git.kernel.org/stable/c/3983ef126e439900bbf419724a9759863c146660CVE reference, Linux
- https://git.kernel.org/stable/c/2a833c730d4e8d1cc10953270ce0f3a156145d81CVE reference, Linux
- https://git.kernel.org/stable/c/c197179990124f991fca220d97fac56779a02c6dCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.