The vulnerability is triggered when an OP‑TEE node is manually defined in the ZynqMP device tree. In normal operation, the OP‑TEE bootloader injects a reserved‑memory node and the firmware node into the kernel device tree. If a device tree already contains an OP‑TEE node, that injection is blocked and the kernel attempts to access memory regions that were never allocated, resulting in a runtime memory access violation. This fault can crash the kernel or allow an attacker to execute code with elevated privileges.

The issue affects Linux kernel deployments on Xilinx ZynqMP platforms where the default device tree includes an OP‑TEE node without the revert commit applied. Any kernel that contains the added OP‑TEE entry in zynqmp.dtsi and does not revert that change is at risk; no specific version range is listed and the workaround is to ensure the revert is present.

The CVSS score is not disclosed and EPSS is unavailable, so formal exploitation probability is unknown. The vulnerability is not in the CISA KEV list, indicating no known public exploits at the time of reporting. Nevertheless, kernel memory access violations carry a high risk; the likely attack vector involves tampering with the device tree during boot or modifying the U‑Boot environment to prevent the reserved‑memory node from being inserted.