The flaw is a lock ordering problem (CWE‑833) in the qcom‑ngd slimbus driver. During a Server‑Side Reset or PDR down notification, the driver acquires tx_lock before the controller lock while other parts of the code grab the controller lock first. This inversion can trigger a lockdep violation and, if the two locks are acquired simultaneously on different CPUs, lead to a deadlock that stalls the kernel and renders the system unresponsive. The bug does not provide a way to read or modify data, so its primary impact is a denial‑of‑service via kernel hang.

The vulnerability affects any Linux kernel that includes the slimbus subsystem with the qcom‑ngd driver and has not yet applied the patch that removes the tx_lock acquisition in qcom_slim_ngd_ssr_pdr_notify. This includes upstream kernels and any distribution kernels built from these sources. Devices using Qualcomm chipset controllers that rely on this driver are therefore impacted.

Based on the description, it is inferred that an attacker would need to trigger a Server‑Side Reset or PDR down notification while a DMA transfer is in progress, a condition that may only be achievable by privileged kernel code or a malicious driver. The EPSS score, reported as less than 1 %, and the absence from the CISA KEV catalog suggest a low likelihood of exploitation. If the vulnerability were exploited, the outcome would be a deadlock that could stall the kernel, causing a denial‑of‑service rather than providing code‑execution capabilities.