Answer in brief
CVE-2026-23466 records a High severity (CVSS 7.8) vulnerability in drm/xe: Open-code GGTT MMIO access protection. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=919bb54e989c1edef87e9797be125c94c450fc65 <e2b424aadecb640f9e037b2891191cf8fd4c64cf || >=919bb54e989c1edef87e9797be125c94c450fc65 <1e9e2640d870d4837bcfdc220cb2c99ae5ee119f || >=919bb54e989c1edef87e9797be125c94c450fc65 <76326dc06d8793c2c81c31cc0115dbc348de2f88 || >=919bb54e989c1edef87e9797be125c94c450fc65 <01f2557aa684e514005541e71a3d01f4cd45c170 | e2b424aadecb640f9e037b2891191cf8fd4c64cf, 1e9e2640d870d4837bcfdc220cb2c99ae5ee119f, 76326dc06d8793c2c81c31cc0115dbc348de2f88, 01f2557aa684e514005541e71a3d01f4cd45c170 |
| Linux/Linuxgeneric | 6.12 | Not reported |
Published upstream
Apr 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 16, 2026
In the Linux kernel, the following vulnerability has been resolved: drm/xe: Open-code GGTT MMIO access protection GGTT MMIO access is currently protected by hotplug (drm_dev_enter), which works correctly when the driver loads successfully and is later unbound or unloaded. However, if driver load fails, this protection is insufficient because drm_dev_unplug() is never called. Additionally, devm release functions cannot guarantee that all BOs with GGTT mappings are destroyed before the GGTT MMIO region is removed, as some BOs may be freed asynchronously by worker threads. To address this, introduce an open-coded flag, protected by the GGTT lock, that guards GGTT MMIO access. The flag is cleared during the dev_fini_ggtt devm release function to ensure MMIO access is disabled once teardown begins. (cherry picked from commit 4f3a998a173b4325c2efd90bdadc6ccd3ad9a431)
Quoted source text, attributed separately from HOL analysis.