CVE-2026-98166

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-10-06. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

drm/ttm: fix swapped-out resources never leaving their bulk_move range

ttm_tt_swapout() returns the number of pages swapped out on success and a negative error code on failure; for a populated ttm it never returns zero. Commit b2ed01e7ad3d ("drm/ttm: Fix ttm_bo_swapout() infinite LRU walk on swapout failure") moved the bulk_move bookkeeping in ttm_bo_swapout_cb() under "if (!ret)", so the ttm_resource_del_bulk_move_unevictable() / ttm_resource_move_to_lru_tail() pair is now skipped on every successful swapout. The equivalent change for the shrinker in commit 1d59f36e95f7 ("drm/ttm: Fix ttm_bo_shrink() infinite LRU walk on backup failure") tests "lret > 0", which is what was intended here as well.

Before b2ed01e7ad3d the resource was taken off the bulk_move before the swapout; since then a swapped-out resource stays inside its BO's bulk_move range (and on the manager LRU) although it is unevictable. When it is later freed or the BO leaves the bulk_move (ttm_resource_free(), ttm_bo_set_bulk_move() via amdgpu_vm_bo_del()), ttm_resource_del_bulk_move() skips it because of its !ttm_resource_unevictable() guard, so a range endpoint in pos->first / pos->last is left pointing at freed memory. The next ttm_lru_bulk_move_tail() or ttm_resource_add_bulk_move() on that cursor is a use-after-free, seen as the resv WARN in ttm_lru_bulk_move_add(), "list_del corruption" in ttm_resource_move_to_lru_tail() or a NULL dereference in ttm_resource_manager_next() -- minutes to hours after a hibernation, or at process exit / reboot following one. Samuel Ainsworth's analysis of drm/amd issue 5387 (see Link) identified the dangling cursor; the missing removal at swapout time is the reason it dangles.

Testing the condition for success restores the removal. On an AMD Phoenix APU (ASUS UM3406GA, gfx1103) running suspend-then-hibernate on a 7.0.y stable kernel carrying the backport (Ubuntu 7.0.0-31) the bug crashed 5 of 18 hibernation cycles; a function profile of one hibernation showed 336 ttm_tt_swapout() calls and zero ttm_resource_del_bulk_move_unevictable() calls. With this change the removal happens for every swapped-out resource and 12 further cycles were clean.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

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.

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 6, 2026

Last Modified

October 7, 2026

Advisory Details (2)

Auto-updated Oct 7, 2026
Patch available.
Web page

drm/ttm: fix swapped-out resources never leaving their bulk_move range - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3db7d7d583419f7b1f2e141e36418802dbb25cf8
Web page

drm/ttm: fix swapped-out resources never leaving their bulk_move range - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1169fe8c11ca45e3f91d59a73eb271d0ca8a7fb0

Vendor Advisories for CVE-2026-98166(1)

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 (181 versions)
  • every version up to 7.2.8-1: fixed in 7.2.8-1
—

Data Freshness Timeline

(refreshed 27× in last 7d / 37× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-10-13 03:59 UTCEG score recompute
  3. 2026-10-13 03:58 UTCGHSA enrichmentGHSA-62xr-3qf5-9qpj · GitHub severity HIGH · GitHub CVSS 7.8
  4. 2026-10-12 14:38 UTCEG score recompute
  5. 2026-10-12 03:48 UTCGHSA enrichmentGHSA-62xr-3qf5-9qpj · GitHub severity HIGH · GitHub CVSS 7.8
  6. 2026-10-11 19:10 UTCEG score recompute
  7. 2026-10-11 16:25 UTCEG score recompute
  8. 2026-10-11 14:56 UTCEG score recompute
  9. 2026-10-11 14:56 UTCGHSA enrichmentGHSA-62xr-3qf5-9qpj · GitHub severity HIGH · GitHub CVSS 7.8
  10. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  11. 2026-10-11 13:37 UTCEG score recompute
  12. 2026-10-11 02:06 UTCEG score recompute
  13. 2026-10-11 02:05 UTCGHSA enrichmentGHSA-62xr-3qf5-9qpj · GitHub severity HIGH · GitHub CVSS 7.8
  14. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  15. 2026-10-10 13:09 UTCGHSA enrichmentGHSA-62xr-3qf5-9qpj · GitHub severity HIGH · GitHub CVSS 7.8
  16. 2026-10-10 00:18 UTCEG score recompute
  17. 2026-10-10 00:18 UTCGHSA enrichmentGHSA-62xr-3qf5-9qpj · GitHub severity HIGH · GitHub CVSS 7.8
  18. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  19. 2026-10-09 11:27 UTCGHSA enrichmentGHSA-62xr-3qf5-9qpj · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-10-08 22:02 UTCEG score recompute
  21. 2026-10-08 22:02 UTCGHSA enrichmentGHSA-62xr-3qf5-9qpj · GitHub severity HIGH · GitHub CVSS 7.8
  22. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  23. 2026-10-08 09:12 UTCEG score recompute
  24. 2026-10-08 09:11 UTCGHSA enrichmentGHSA-62xr-3qf5-9qpj · GitHub severity HIGH · GitHub CVSS 7.8
  25. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
Show 12 more
  1. 2026-10-07 20:20 UTCEG score recompute
  2. 2026-10-07 20:20 UTCGHSA enrichmentGHSA-62xr-3qf5-9qpj · GitHub severity HIGH · GitHub CVSS 7.8
  3. 2026-10-07 07:29 UTCEG score recompute
  4. 2026-10-07 07:29 UTCGHSA enrichmentGHSA-62xr-3qf5-9qpj
  5. 2026-10-07 06:58 UTCEG score recomputeFirst assessed: 7.8 HIGH
  6. 2026-10-07 06:58 UTCGHSA enrichmentGHSA-62xr-3qf5-9qpj
  7. 2026-10-07 06:56 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  8. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-10-06 09:53 UTCGHSA enrichmentGHSA-62xr-3qf5-9qpj
  10. 2026-10-06 09:28 UTCNVD update
  11. 2026-10-06 08:56 UTCEG score recompute
  12. 2026-10-06 08:52 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-98166?
CVE-2026-98166 is a high-severity vulnerability; its CVE record was published on October 6, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/ttm: fix swapped-out resources never leaving their bulk_move range ttmttswapout() returns the number of pages swapped out on success and a negative error code on failure; for a populated ttm it never returns zero. Commit…
When was the CVE record for CVE-2026-98166 published?
The CVE record for CVE-2026-98166 was published on October 6, 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 October 7, 2026; the record at its source may have been updated since.
Is CVE-2026-98166 actively exploited?
CVE-2026-98166 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-98166?
CVE-2026-98166 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-98166?
A fix for CVE-2026-98166 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-98166 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-98166

Explore →

Is Your Infrastructure Affected by CVE-2026-98166?

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

Book a Demo →Browse All CVEs