# CVE-2026-99210: accel/rocket: clear rdev on device init failure


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** BELL-CVE-2026-99210, DEBIAN-CVE-2026-99210, GHSA-7q2q-xjhr-934r, UBUNTU-CVE-2026-99210

## What is CVE-2026-99210?

CVE-2026-99210 is a vulnerability in Linux, published on 28 Oct 2026. 

### Official 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.

## Which versions are affected by CVE-2026-99210?


## How do I fix CVE-2026-99210?

Upgrade to a fixed version.

## Is CVE-2026-99210 being exploited?

There is no known exploitation of CVE-2026-99210 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-99210 and fix it if it is affected.

What it is: CVE-2026-99210 is a vulnerability in Linux, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99210 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-99210/ (Markdown: https://insights.sbomify.com/CVE-2026-99210/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-99210
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99210
- OSV: https://osv.dev/vulnerability/CVE-2026-99210

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-99210/
Summaries are generated and may contain mistakes; the official description above is the record.