VulnerabilityPublished 28 Oct 2026

CVE-2026-99184: Linux kernel · accel/rocket: search every core slot when a core is removed

Source GCVE Database

Authoritative record:CVE-2026-99184

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

Data as of 28 Oct 2026, 13:43 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch: Available – fixed in 134451cf95cb6aa04b725fbfa04e878d072756f5, 5078c91f5c84bb383d0a10ed39856f98575e39cf, 6eff1d69dae808a1518aee5a58d0853a8db3f1be

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.

ghsa-fqrq-qcw6-wmqq

What to do

Upgrade Linux kernel to 134451cf95cb6aa04b725fbfa04e878d072756f5, 5078c91f5c84bb383d0a10ed39856f98575e39cf or 6eff1d69dae808a1518aee5a58d0853a8db3f1be.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ ed98261b41687323ffa02ca20fef1e60b38fd1aa, < 134451cf95cb6aa04b725fbfa04e878d072756f5	Fixed in 134451cf95cb6aa04b725fbfa04e878d072756f5
LinuxLinux	Affected ≥ ed98261b41687323ffa02ca20fef1e60b38fd1aa, < 5078c91f5c84bb383d0a10ed39856f98575e39cf	Fixed in 5078c91f5c84bb383d0a10ed39856f98575e39cf
LinuxLinux	Affected ≥ ed98261b41687323ffa02ca20fef1e60b38fd1aa, < 6eff1d69dae808a1518aee5a58d0853a8db3f1be	Fixed in 6eff1d69dae808a1518aee5a58d0853a8db3f1be
LinuxLinux	Affected =6.18	Fixed in–
Debiandebian/linux`pkg:deb/debian/linux`Other threats	Affected =6.18	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix has been applied that records the number of allocated core slots and searches all of them during core removal, ensuring proper cleanup and preventing stale core counts. Users should update to the fixed Linux kernel version containing this patch. Since the vulnerability affects kernel driver internals, no additional mitigation steps are indicated. Further improvements are needed to safely handle rebinding of individual cores while siblings remain bound.

Description

A vulnerability in the Linux kernel's accel/rocket driver causes an out-of-bounds write when cores are unbound and rebound. The issue arises because rocket_remove() decrements the core count while find_core_for_dev() searches only up to the decremented count, causing the last core slot to be skipped. This leads to a stale core count and an out-of-bounds write when rebinding cores, potentially corrupting memory silently.

Impact

This vulnerability causes a silent out-of-bounds write in kernel memory when cores are unbound and rebound, which can lead to memory corruption. Although no direct exploitation or active attacks are reported, the memory corruption could potentially destabilize the kernel or cause undefined behavior. The issue was found during testing on specific hardware (RK3588 and Orange Pi 5 Plus). There is no indication of remote exploitability or privilege escalation from the provided data.

References

Community reviews

Loading reviews…