# CVE-2025-71300: linux: In the Linux kernel, the following vulnerability has been resolved:  Revert "arm64: zynqmp: Add an OP-TEE node to the...

CVE-2025-71300 is fixed in linux on 1 platform, first by DEBIAN-CVE-2025-71300, released May 15, 2026. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2025-71300
- Priority: Routine
- CVSS: 5.5 (medium)
- EPSS: 0.0015
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: May 8, 2026

## 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.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 13.5 (trixie) | 6.12.85-1 | [DEBIAN-CVE-2025-71300](https://patchblox.com/security/data/fix/linux/debian-cve-2025-71300.md) | May 15, 2026 |
| Linux | linux Debian 14 | 6.19.6-1 | [DEBIAN-CVE-2025-71300](https://patchblox.com/security/data/fix/linux/debian-cve-2025-71300.md) | May 15, 2026 |

---

Data as of 2026-11-10T01:44:33Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.