The flaw resides in the debugobject subsystem of memory during the early boot phase of a PREEMPT_RT‑enabled system on ARM64. While the kernel is still enabling interrupts prior to the activation of the scheduler, an interrupt handler may invoke an allocation routine that holds a lock conflicting with a lock that debugobjects requires. This lock‑order violation can trigger a deadlock, manifested by a hang during boot. The vulnerability is identified as a CWE‑833, a race condition that leads to a lock deadlock. It does not directly compromise data confidentiality or integrity; its primary impact is a denial of service that interrupts the ability of the host to boot normally.

Kernels built for the ARM64 architecture that enable the PREEMPT_RT patch set and the CONFIG_DEBUG_PREEMPT_RT configuration are impacted. Versions of the Linux kernel released prior to the incorporation of the commits adding a can_fill_pool() guard and reordering the exception rule. Most embedded or real‑time deployments that rely on early‑boot debugging features are likely affected.

The CVSS score of 5.5 indicates medium severity. The EPSS score of less than 1% reflects an extremely low likelihood that this vulnerability will be actively exploited. Based on the description, the attack vector is local and confined to the system during its boot sequence; a remote attacker would not be able to influence interrupt timing before scheduler start‑up. The vulnerability does not mention any effect on data confidentiality or integrity, so it is inferred that these properties are not compromised by the flaw. The practical risk therefore manifests as a boot‑time denial of service. This vulnerability is not listed in the CISA KEV catalog, indicating no known active exploitation in the wild.