CVE-2026-99210

accel/rocket: clear rdev on device init failure

Published Oct 28, 2026 CVSS 3.1 · 4.1 Medium EPSS < 1% KEV · Not listed
Description
In 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.

Analysis

AI-generated

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.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the kernel to the latest version that contains the commit fixing the accel/rocket driver
  • Reboot the system so the updated kernel module loads
  • If an immediate kernel upgrade is not possible, disable the accel/rocket driver (e.g., modprobe -r accel_rocket) to prevent the fault until a patch is applied

Generated by OpenCVE AI on October 29, 2026 at 18:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-12
Type Values Removed Values Added
Weaknesses CWE-252
References
Metrics threat_severity

None

cvssV3_1

{'score': 4.1, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux
Type Values Removed Values Added
Weaknesses CWE-12
Type Values Removed Values Added
Description In 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.
Title accel/rocket: clear rdev on device init failure
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 28, 2026, 10:36 AM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Oct 28, 2026, 11:17 AM
Modified
Oct 28, 2026, 11:17 AM
Severity
Moderate
Public date
Oct 28, 2026, 12:00 AM