CVE-2026-23466
Improper MMIO Access Control in Linux drm/xe Causes Privilege Risk
Publication date: 2026-04-03
Last updated on: 2026-04-27
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's drm/xe component related to GGTT MMIO access protection. Normally, GGTT MMIO access is protected by a mechanism called hotplug (drm_dev_enter), which works correctly when the driver loads successfully and is later unbound or unloaded. However, if the driver fails to load, this protection does not work properly because the cleanup function drm_dev_unplug() is never called.
Additionally, the existing resource management functions (devm release functions) cannot guarantee that all buffer objects (BOs) with GGTT mappings are destroyed before the GGTT MMIO region is removed, since some BOs may be freed asynchronously by worker threads.
To fix this, a new open-coded flag protected by the GGTT lock was introduced to guard GGTT MMIO access. This flag is cleared during the dev_fini_ggtt devm release function to ensure MMIO access is disabled once teardown begins, preventing unauthorized access.
How can this vulnerability impact me? :
If exploited, this vulnerability could allow unauthorized or unintended access to GGTT MMIO regions in the Linux kernel, especially in cases where the driver fails to load properly. This could potentially lead to security issues such as unauthorized memory access or corruption within the graphics subsystem.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability in the Linux kernel related to GGTT MMIO access protection has been resolved by introducing an open-coded flag protected by the GGTT lock to guard GGTT MMIO access. To mitigate this vulnerability, you should ensure that your Linux kernel is updated to a version that includes this fix.
This fix addresses the issue where protection was insufficient if the driver load failed and ensures that MMIO access is disabled once teardown begins.