Technical impact
This kernel flaw traps the rocket accelerator subsystem in a state where an inactive core remains bound but its address is omitted from the active search list after an intermediate core is removed. The lookup function then returns a null pointer, and subsequent code paths—such as job execution and timeout handling—dereference this pointer without verification. The faults manifest as kernel memory errors and, if not mitigated, can lead to full system crashes or loss of GPU service. The core problem is a classic null pointer dereference caused by incorrect array bounds handling within the scheduling code.
Affected Systems
The issue resides in the Linux kernel’s rocket accelerator (accel/rocket) module. It applies to any distribution or build that uses the rocket scheduler, including newer platforms such as the RK3588 where the accelerator is active. No specific kernel series or patch level is provided, so all kernels that incorporate the rocket subsystem before the commit that adds the bounds check are potentially vulnerable.
Risk and Exploitability
The kernel panic manifests as a denial‑of‑service. The flaw also causes clients to wait on fences that never complete. No public exploit data exists. The CVSS score of 4.4 indicates moderate severity. The EPSS score of < 1% indicates a low likelihood of exploitation. The vulnerability remains a priority for all affected kernel distributions.