accel/rocket: fix unwinding in error path in rocket_probe
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.176.19.77.0In the Linux kernel, the following vulnerability has been resolved:
accel/rocket: fix unwinding in error path in rocket_probe
When rocket_core_init() fails (as could be the case with EPROBE_DEFER), we need to properly unwind by decrementing the counter we just incremented and if this is the first core we failed to probe, remove the rocket DRM device with rocket_device_fini() as well. This matches the logic in rocket_remove(). Failing to properly unwind results in out-of-bounds accesses.
From the CVE record · Linux
The Linux kernel’s accel/rocket driver fails to properly unwind when rocket_core_init() fails during rocket_probe, potentially causing out-of-bounds accesses. The input does not describe an attack path or specify network access, authentication, or user-interaction requirements.
Engineers running Linux kernels with the accel/rocket driver should check their affected versions; no version range was provided.