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 5.5, EPSS is <1%, and KEV is not listed, indicating no publicly known exploits at the time of reporting. The moderate severity score reflects the risk of a memory access violation that could crash the kernel or facilitate privilege escalation if an attacker can tamper with the device tree or U‑Boot on a ZynqMP platform. The likely attack vector is manipulating the boot environment to prevent the OP‑TEE node injection, causing the kernel to access unallocated memory.