CVE-2026-99183

UNRATEDCVSS · not yet scored

Also known asEUVD-2026-111935 (ENISA EUVD) · GHSA-cgc9-44mx-vhwg (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

accel/rocket: search every core slot when looking up a scheduler

sched_to_core() walks rdev->cores[] up to rdev->num_cores, and rocket_remove() decrements num_cores for every core it removes. Unbind a core that is not the last one and the cores behind it fall outside the search, so sched_to_core() returns NULL for a core that is still bound and still running jobs. Neither caller checks the result:

rocket_job_run(): rocket_fence_create(core), core->dev rocket_job_timedout(): dev_err(core->dev, "NPU job timed out")

Unbinding the middle core of the three on an RK3588 while three clients are submitting to all of them faults twice, once from the surviving core's job queue and once from its reset work:

KASAN: null-ptr-deref in range [0x0000000000000220-0x0000000000000227] Workqueue: fdad0000.npu drm_sched_run_job_work [gpu_sched] pc : rocket_job_run+0x234/0x838 [rocket] Call trace: rocket_job_run+0x234/0x838 [rocket] drm_sched_run_job_work+0x2cc/0xad8 [gpu_sched] process_one_work+0x640/0x14f0

KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] Workqueue: rocket-reset-2 drm_sched_job_timedout [gpu_sched] pc : rocket_job_timedout+0xf0/0x1e0 [rocket] Call trace: rocket_job_timedout+0xf0/0x1e0 [rocket] drm_sched_job_timedout+0x188/0x6a0 [gpu_sched]

Both are the third core: the workqueue names are its device and its core->index, and it was left at slot 2 while num_cores had dropped to 2.

Search all the slots that were allocated, the way find_core_for_dev() now does. A core that is still bound is then found, and the two callers get the pointer they already assume they have.

This does not make unbinding one core out of several safe. An open client keeps an entity pointing at the scheduler of the core that went away: drm_sched reports it as not ready for every job that lands on it, and the client waits in dma_fence_default_wait for a fence that will never signal. Stopping the NULL dereference is what belongs in a fix; the rest wants more thought.

CVSS
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 28, 2026

Last Modified

November 6, 2026

Vendor Advisories for CVE-2026-99183(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (192 versions)
  • every version up to 7.2.13-1: fixed in 7.2.13-1
—

Data Freshness Timeline

(refreshed 6× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  4. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-11-16 16:54 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-11-15 17:04 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-11-13 16:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-11-09 16:37 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  15. 2026-11-06 18:29 UTCGHSA enrichmentGHSA-cgc9-44mx-vhwg
  16. 2026-11-06 18:26 UTCNVD update
  17. 2026-11-06 17:23 UTCEchelonGraph re-scored
  18. 2026-11-06 17:23 UTCGHSA enrichmentGHSA-cgc9-44mx-vhwg
  19. 2026-11-06 17:22 UTCMITRE cvelistV5
  20. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  22. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 4th percentile
Show 7 more
  1. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-10-28 11:26 UTCNVD update
  5. 2026-10-28 11:01 UTCENISA EUVD ID recordedEUVD-2026-111935 · Source: ENISA EUVD
  6. 2026-10-28 10:45 UTCEchelonGraph re-scored
  7. 2026-10-28 10:44 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-99183?
CVE-2026-99183 is a vulnerability whose severity is not yet rated; its CVE record was published on October 28, 2026. In the Linux kernel, the following vulnerability has been resolved: accel/rocket: search every core slot when looking up a scheduler sched_to_core() walks rdev->cores[] up to rdev->num_cores, and rocket_remove() decrements num_cores for every core it removes. Unbind a core that is not the last one…
When was the CVE record for CVE-2026-99183 published?
The CVE record for CVE-2026-99183 was published on October 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 6, 2026; the record at its source may have been updated since.
Is CVE-2026-99183 actively exploited?
CVE-2026-99183 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-99183?
A fix for CVE-2026-99183 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-99183 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-99183

Explore →

Is Your Infrastructure Affected by CVE-2026-99183?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.