A race condition in the Qualcomm SLIMBus NGD controller driver causes callbacks to be registered and invoked before the NGD device is fully initialized. When a remote‑processor starts or a hardware interrupt occurs concurrently with the driver probe, the driver may dereference a null pointer, leading to a kernel panic during boot. This flaw is a classic null reference error that can prevent the board from booting normally.

Linux kernel builds that include the slimbus/qcom‑ngd‑ctrl module on Qualcomm platforms using the SLIMBus interconnect are affected. Any kernel version that has not integrated the upstream patch and still loads this module at startup is vulnerable. Systems that omit the module or run a patched kernel are not at risk.

The EPSS score of <1 % and the absence from CISA’s KEV catalog indicate a low likelihood of exploitation in the wild. Based on the description, it is inferred that exploitation would require an attacker with privileged access to the device, capable of manipulating the timing of remote‑processor initialization or triggering hardware interrupts during driver probe. Successful exploitation would cause a kernel panic, halting the system and preventing normal boot, resulting in a denial of service.