Vulnerability · Published Aug 15, 2026 · Assigned by Linux

CVE-2026-72358drm/xe/pt: prevent invalid cursor access for purged BOs

High 7.8

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 6% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.2%top 94.2% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: drm/xe/pt: prevent invalid cursor access for purged BOs During a page table walk for binding, xe_pt_stage_bind() explicitly skips initializing the xe_res_cursor for purged BOs, treating them similarly to NULL VMAs by only setting the cursor size. However, xe_pt_hugepte_possible() and xe_pt_scan_64K() did not check if the BO was purged before attempting to walk the cursor using xe_res_dma() and xe_res_next(). Because the cursor was left uninitialized for purged BOs, this falls through and triggers warnings like: WARNING: drivers/gpu/drm/xe/xe_res_cursor.h:274 at xe_res_next Fix this by explicitly checking if the BO is purged in both xe_pt_hugepte_possible() and xe_pt_scan_64K(), returning early just as we do for NULL VMAs, avoiding the invalid cursor accesses entirely. As a precaution, also zero-initialize the cursor in xe_pt_stage_bind() to ensure we don't pass garbage data into the page table walkers if we ever hit a similar edge case in the future. (cherry picked from commit 4c7b9c6ece32440e5a435a92076d049450cd2d2e)

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:14linux7.1.5-1DEBIAN-CVE-2026-72358
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-72358
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-72358
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-72358

Affected products (as reported)

VendorProductVersions
Linux Linux ad9843aac91a1eda12912a4922042ea04cfc29dc – before 2b6b3f98d0e93856bee38699b783c71cb0e9d67fad9843aac91a1eda12912a4922042ea04cfc29dc – before 8a0fb57675be578c4db19deb4298ed08a70f0f1a
Linux Linux 7.1

References