CVE-2026-99210: accel/rocket: clear rdev on device init failure
In the Linux kernel, the following vulnerability has been resolved:
accel/rocket: clear rdev on device init failure
rocketprobe() stores the return value from rocketdeviceinit() in the file-scoped rdev pointer before checking whether it is an error pointer. If rocketdeviceinit() fails, rdev is left as an ERRPTR.
The rdev pointer is also used as the marker for whether the shared rocket device has already been initialized. A later core probe can therefore see a non-NULL rdev, skip rocketdeviceinit(), and dereference the error pointer when reading rdev->numcores.
Save the error code and clear rdev before returning from the rocketdeviceinit() failure path.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.59 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.2.13 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.2.13-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.116-1Fixed in 7.2.15-1Fixed in 7.3.3-1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.3.0-10.10 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-azureto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-azure-fdeto a version that resolves this vulnerability.Fixed in 7.3.0-1004.5 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-raspito a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-realtimeto a version that resolves this vulnerability.Fixed in 7.3.0-10.10.1 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.3.0-10.10.1
Event History
Frequently Asked Questions
When can this issue be triggered?
It requires rocket_device_init() to fail during a core probe. A later core probe must then occur; it can see the stale non-NULL rdev error pointer, skip shared-device initialization, and dereference that error pointer while reading rdev->num_cores.
What is the practical impact of the faulty state?
After an initialization failure, the shared rdev marker remains an ERR_PTR rather than being cleared. Subsequent probing can treat the failed initialization as successful and dereference the invalid pointer.
How can I determine whether a system may have encountered the vulnerable path?
Look for a rocket device initialization failure followed by another core probe. The vulnerable sequence is specifically an initial rocket_device_init() failure followed by a later probe that accesses rdev->num_cores without reinitializing the shared device.