The flaw occurs when a Rust-based IRQ registration component invokes request_irq() before fully initializing its internal data structure. The interrupt request is enabled while the cookie structure remains incomplete, causing the interrupt handler to read fields that contain garbage data. This uninitialized memory use can lead to silent corruption, kernel crashes, or inadvertent exposure of stack contents. The weakness reflects classic uninitialized memory usage and a race condition during device initialization.

Custom Linux kernel builds that still contain the legacy Rust IRQ registration path—those compiled before the commit that removed Devres from irq::Registration (commit 98c63ce4) are affected. Mainline distributions have been restructured to eliminate the race condition, so they are not impacted. Users of experimental or in-house kernels that retain the legacy Rust IRQ code may be vulnerable if the safe rewrite has not been applied.

No EPSS score is available and the vulnerability is not listed in CISA KEV, indicating limited public exploitation. However, the scenario requires kernel-level access and can lead to denial of service or information disclosure if an attacker triggers the IRQ callback during the race window. The absence of a published CVSS score prevents a precise severity rating, but the potential impact on system stability and confidentiality suggests a moderate to high risk for affected custom kernel builds.