VulnerabilityPublished 28 Oct 2026

CVE-2026-99210: Linux kernel · accel/rocket: clear rdev on device init failure

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in dd47a6c920083b069f00f0920e4566915a6aec46 : update Linux kernel when convenient.

Data as of 28 Oct 2026, 10:58 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Patch: Available – fixed in dd47a6c920083b069f00f0920e4566915a6aec46, 79071b67182e1b352d51a3917729b8d424710b49, 4ac852419f0d317c7bd8db5b8acb3cc78be7fe33

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to dd47a6c920083b069f00f0920e4566915a6aec46, 79071b67182e1b352d51a3917729b8d424710b49 or 4ac852419f0d317c7bd8db5b8acb3cc78be7fe33.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ ed98261b41687323ffa02ca20fef1e60b38fd1aa, < dd47a6c920083b069f00f0920e4566915a6aec46	Fixed in dd47a6c920083b069f00f0920e4566915a6aec46
LinuxLinux	Affected ≥ ed98261b41687323ffa02ca20fef1e60b38fd1aa, < 79071b67182e1b352d51a3917729b8d424710b49	Fixed in 79071b67182e1b352d51a3917729b8d424710b49
LinuxLinux	Affected ≥ ed98261b41687323ffa02ca20fef1e60b38fd1aa, < 4ac852419f0d317c7bd8db5b8acb3cc78be7fe33	Fixed in 4ac852419f0d317c7bd8db5b8acb3cc78be7fe33
LinuxLinux	Affected =6.18	Fixed in–

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.

References

Community reviews

Loading reviews…