Linux kernel probe failure in Rocket accelerator initialization
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.597.2.137.3In the Linux kernel, the following vulnerability has been resolved:
accel/rocket: clear rdev on device init failure
rocket_probe() stores the return value from rocket_device_init() in the file-scoped rdev pointer before checking whether it is an error pointer. If rocket_device_init() fails, rdev is left as an ERR_PTR.
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 rocket_device_init(), and dereference the error pointer when reading rdev->num_cores.
Save the error code and clear rdev before returning from the rocket_device_init() failure path.
From the CVE record · Linux
The Linux kernel's accel/rocket driver can leave its shared device pointer set to an error pointer when device initialization fails. If another core is probed later, it can dereference that pointer. The input does not establish how an attacker could trigger this condition or whether authentication or user interaction is required.
Teams running Linux kernels with the accel/rocket driver should check their versions; affected versions were not provided.