CVE-2026-23466 Details
Description
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)
A vulnerability in the Linux kernel's handling of Graphics Translation Table (GGTT) Memory-Mapped I/O (MMIO) access within the Direct Rendering Manager (DRM) Xe component has been addressed. The issue arose because GGTT MMIO access relied on hotplug events, which only functioned correctly when the driver loaded successfully. In cases of driver load failure, the necessary unplugging process was not executed, leaving a gap in protection. Furthermore, the device management release functions could not ensure that all Buffer Objects (BOs) with GGTT mappings were cleared before the GGTT MMIO region was removed, as some BOs might be released asynchronously by worker threads. This vulnerability could potentially be exploited by manipulating the timing of BO releases in relation to GGTT MMIO region removals.
The vulnerability has been fixed by introducing an open-coded flag that is protected by the GGTT lock, which now guards GGTT MMIO access. This flag is cleared during the device management release process to ensure that MMIO access is disabled before the GGTT region is removed. Users should update to the latest version of the Linux kernel where this fix has been applied.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Oct 16, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/01f2557aa684e514005541e71a3d01f4cd45c170 | kernel.org | Patch |
| https://git.kernel.org/stable/c/1e9e2640d870d4837bcfdc220cb2c99ae5ee119f | kernel.org | Patch |
| https://git.kernel.org/stable/c/76326dc06d8793c2c81c31cc0115dbc348de2f88 | kernel.org | Patch |
| https://git.kernel.org/stable/c/e2b424aadecb640f9e037b2891191cf8fd4c64cf | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
| CWE-362 | Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') | CISA-ADP |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.12, < 6.12.78 >= 6.13, < 6.18.20 >= 6.19, < 6.19.10 7.0 rc1 7.0 rc2 7.0 rc3 7.0 rc4 |
CPE
Remediation
| |
Change History
8 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 19, 2026 | CVE Modified | CISA-ADP |
| Oct 16, 2026 | CVE Modified | kernel.org |
| Oct 16, 2026 | CVE Modified | CISA-ADP |
| Jul 24, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| May 20, 2026 | Initial Analysis | [email protected] |
| Apr 27, 2026 | CVE Modified | kernel.org |
| Apr 3, 2026 | New CVE Received | kernel.org |