CVE-2026-98106

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory (severity: MODERATE) published 2026-09-25. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-86937 (ENISA EUVD) · GHSA-94vc-8r96-mrjf (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

drm/pagemap: Prevent double migration of device pages

A device-private folio migrated to system memory by a CPU fault can remain reachable through the raw-PFN eviction path until migration finalization drops the source reference.

If eviction selects the same device-private folio during this window, it can attempt to migrate the folio again. The second migration can leave an uncharged folio on an LRU list, causing folio_lruvec_lock_irqsave() to retry indefinitely and resulting in a soft lockup and RCU stall.

Mark successfully migrated device-private folios using a low bit of their zone_device_data before migration finalization. Make both CPU-fault and raw-PFN migration paths skip device-private folios carrying this flag.

Mask the flag when retrieving the drm_pagemap_zdd pointer and preserve it when a device-private folio is split. Keeping the state on the physical folio also avoids depending on a virtual address that may change before a fault occurs.

v2:

  • Replace the retired-PFN XArray with an embedded bitmap. (Matthew Brost)
  • Mark every base page covered by a migrated folio so retirement remains
valid if the folio is later split.

v3:

  • Store the migrated state in a low bit of zone_device_data instead of
adding virtual-range and bitmap tracking to the ZDD. (Matthew Brost)
  • Mask the flag when retrieving the ZDD and preserve it when splitting
a folio.
  • Drop the pre-existing fixes already covered by Matthew Brost's series:
https://patchwork.freedesktop.org/series/171651/

v4:

  • Advance by the folio size only for migration entries marked with
MIGRATE_PFN_COMPOUND. (Sashiko)

v5:

  • Simplify ZDD flag updates and folio iteration. (Matthew Brost)
  • Skip retired device-private folios in the CPU-fault path. (Matthew Brost)
  • Preserve flag bits while taking a new ZDD reference for split folios.

v6:

  • Restore MIGRATE_PFN_COMPOUND-aware stepping so non-compound migration
entries are processed one at a time. (Sashiko)
  • Drop the pre-existing fixes already covered by Matthew Brost's series:
https://patchwork.freedesktop.org/series/171651/

The lockup was observed as: [10109.860465] watchdog: BUG: soft lockup - CPU#9 stuck for 26s! [kworker/u65:5:6557] [10109.860524] Tainted: [S]=CPU_OUT_OF_SPEC, [O]=OOT_MODULE [10109.860524] Hardware name: ASUS System Product Name/PRIME Z790-P WIFI, BIOS 0812 02/24/2023 [10109.860525] Workqueue: xe_page_fault_work_queue xe_pagefault_queue_work [xe] [10109.860644] RIP: 0010:_raw_spin_unlock_irqrestore+0x57/0x80 [10109.860655] Call Trace: [10109.860655] [10109.860657] folio_lruvec_lock_irqsave+0x216/0x220 [10109.860661] ? __pfx_lru_add+0x10/0x10 [10109.860665] folio_batch_move_lru+0xc8/0x450 [10109.860670] ? lock_acquire+0xc4/0x2d0 [10109.860674] ? __folio_batch_add_and_move+0x60/0x2e0 [10109.860677] ? folio_migrate_mapping+0xa6/0x110 [10109.860679] ? folio_migrate_flags+0x13b/0x1b0 [10109.860681] ? __pfx_lru_add+0x10/0x10 [10109.860683] __folio_batch_add_and_move+0xe7/0x2e0 [10109.860685] ? dma_iova_try_alloc+0xb0/0x140 [10109.860689] folio_add_lru+0x64/0x80 [10109.860691] __migrate_device_finalize+0x12c/0x270 [10109.860695] migrate_device_finalize+0x10/0x20 [10109.860698] drm_pagemap_evict_to_ram+0x185/0x370 [drm_gpusvm_helper] [10109.860704] ? drm_pagemap_evict_to_ram+0x96/0x370 [drm_gpusvm_helper] [10109.860709] xe_svm_bo_evict+0x15/0x20 [xe] [10109.860819] ? xe_svm_bo_evict+0x15/0x20 [xe] [10109.860921] xe_bo_move+0x107e/0x1570 [xe] [10109.860992] ? xe_ttm_tt_create+0x168/0x340 [xe] [10109.861059] ? __up_read+0x98/0x2b0 [10109.861061] ? lock_is_held_type+0xa3/0x130 [10109.861067] ttm_bo_handle_move_mem+0xe8/0x1e0 [ttm] [10109.861075] ttm_bo_evict+0x141/0x1c0 [ttm] [10109.861081] ttm_bo_evict_cb+0x9f/0x100 [ttm] [10109.861086] ttm_lru_walk_for_evict+0x84/0x190 [ttm] [10109.861091] ? xe_ttm_vram_mgr_new+0x258/0x3a0 [xe] [10109.861198] ttm_bo_alloc_resource+0x219/0 ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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.1%
EPSS %ILE
below the 1st
KEV
Not listed

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

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
<0.1% 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
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA 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 SSVC and BOD 26-04 blocks below.

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.

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

September 25, 2026

Last Modified

November 12, 2026

References (2)

Vendor Advisories for CVE-2026-98106(2)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 7.2.7 (fixes >=6.15.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

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.7-1: fixed in 7.2.7-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× 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 its CVE.org record (CNA or CISA ADP). 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). "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.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 74 is merged into the row it repeats.

  1. 2026-11-13 16:58 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  2. 2026-11-12 18:48 UTCEchelonGraph re-scoredFirst assessed: 5.5 MEDIUM
  3. 2026-11-12 18:48 UTCGHSA enrichmentGHSA-94vc-8r96-mrjf · GitHub severity MODERATE · GitHub CVSS 5.5
  4. 2026-11-12 18:47 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  5. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  6. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  7. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  8. 2026-11-09 16:37 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  14. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-10-28 09:25 UTCOSV refresh
  22. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-10-25 13:47 UTCEchelonGraph re-scored
Show 48 more
  1. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  5. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  6. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  7. 2026-10-19 10:36 UTCGHSA enrichmentGHSA-94vc-8r96-mrjf
  8. 2026-10-19 10:25 UTCNVD update
  9. 2026-10-19 09:51 UTCEchelonGraph re-scored
  10. 2026-10-19 09:51 UTCGHSA enrichmentGHSA-94vc-8r96-mrjf
  11. 2026-10-19 09:39 UTCMITRE cvelistV5
  12. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-10-18 02:56 UTCEchelonGraph re-scored
  14. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-10-12 14:39 UTCEchelonGraph re-scored
  21. 2026-10-11 19:10 UTCEchelonGraph re-scored
  22. 2026-10-11 16:25 UTCEchelonGraph re-scored
  23. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-10-11 13:37 UTCEchelonGraph re-scored
  25. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  26. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  27. 2026-10-09 08:27 UTCGHSA enrichmentGHSA-94vc-8r96-mrjf
  28. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  29. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  30. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  31. 2026-10-06 10:29 UTCGHSA enrichmentGHSA-94vc-8r96-mrjf
  32. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  33. 2026-10-04 23:23 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  34. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  35. 2026-10-03 12:32 UTCGHSA enrichmentGHSA-94vc-8r96-mrjf
  36. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  37. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  38. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  39. 2026-09-30 14:34 UTCEchelonGraph re-scored
  40. 2026-09-30 14:34 UTCGHSA enrichmentGHSA-94vc-8r96-mrjf
  41. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  42. 2026-09-28 09:29 UTCEchelonGraph re-scored
  43. 2026-09-28 09:29 UTCGHSA enrichmentGHSA-94vc-8r96-mrjf
  44. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  45. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  46. 2026-09-25 11:30 UTCNVD update
  47. 2026-09-25 10:48 UTCEchelonGraph re-scored
  48. 2026-09-25 10:46 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-98106?
CVE-2026-98106 is a medium-severity vulnerability; its CVE record was published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/pagemap: Prevent double migration of device pages A device-private folio migrated to system memory by a CPU fault can remain reachable through the raw-PFN eviction path until migration finalization drops the source reference.…
When was the CVE record for CVE-2026-98106 published?
The CVE record for CVE-2026-98106 was published on September 25, 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 12, 2026; the record at its source may have been updated since.
Is CVE-2026-98106 actively exploited?
CVE-2026-98106 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-98106?
CVE-2026-98106 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-98106?
A fix for CVE-2026-98106 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-98106 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-98106

Explore →

Is Your Infrastructure Affected by CVE-2026-98106?

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

Book a Demo →Browse All CVEs