Technical impact
The accel/rocket driver in the Linux kernel stores an error pointer returned from rocket_device_init() in a global rdev variable before verifying it is an actual pointer. If initialization fails, rdev becomes an ERR_PTR value. Subsequent probe code assumes a non‑NULL rdev indicates a fully initialized device and uses it to read num_cores, dereferencing the erroneous pointer. This unchecked return value and improper error handling cause an invalid pointer dereference that results in a kernel panic, effectively denying service. The flaw is exploitable only when the attacker can induce a device‑initialization failure, such as by presenting malformed hardware or misconfiguring the device, which may allow a local privileged or user process to trigger the crash. Based on the description, it is inferred that the attacker would need local access to initiate the device‑initialization failure.
Affected Systems
All Linux kernel builds that include the accel/rocket module before the commit that introduced the fix (4ac852419f0d317c7bd8db5b8acb3cc78be7fe33) are vulnerable. The affected code lives in drivers/accel/rocket.c and can be present in any distribution that uses a kernel version earlier than the patch. The vulnerability is not tied to a specific distribution release and therefore applies across all platforms that ship the kernel with the unpatched driver.
Risk and Exploitability
The EPSS score is below 1%, and the vulnerability is not listed in the CISA KEV catalog, indicating minimal current exploitation activity. The CVSS score of 4.1 reflects a medium severity. An attacker needs local access to the kernel or the ability to make rocket_device_init() fail. Once triggered, the crash can lead to a denial of service, and in some cases could be leveraged for privilege escalation if other kernel paths are abused after the panic. Remote exploitation is unlikely unless an attacker can influence the device initialization from outside the kernel. The likely attack vector is local, inferred from the need for the device‑initialization failure and the lack of any exposed remote interface.