CVE-2026-72359: drm/xe: fix NPD in bo_meminfo()

Published Aug 15, 2026
·
Updated

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

drm/xe: fix NPD in bomeminfo()

When a buffer object is purged, its ttm.resource is set to NULL via the TTM pipeline gutting flow. However, the BO remains in the client's object list until userspace explicitly closes the GEM handle. If memory stats are queried during this time, accessing bo->ttm.resource->memtype will result in a NULL pointer dereference.

Fix this by safely skipping purged BOs in bomeminfo, as they no longer consume any memory.

User is getting NPD on device resume, and possible theory is that in bomove(), if we need to evict something to SYSTEM to save the CCS state, but the BO is marked as dontneed, this won't trigger a move but will nuke the pages, leaving us with a NULL bo resource. And the meminfo() doesn't look ready to handle a NULL resource.

v2 (Sashiko): - There could potentially be other cases where we might end up with a NULL resource, so make this a general NULL check for now.

(cherry picked from commit c9a8e7daa0afe3161111e27fd92176e608c7f186)

Affected Software

1 affected component
Linux Linux kernel (drm/xe)

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Linux kernel (drm/xe) to a version that resolves this vulnerability.

    Fixed in v2 (Sashiko)
  2. Configuration

    Fix the NULL pointer dereference by safely skipping purged BOs in bo_meminfo(), making the code handle the general case where ttm.resource is NULL instead of unconditionally accessing bo->ttm.resource->mem_type.

    drm/xe bo_meminfo() = Add a safe NULL check to skip purged buffer objects whose ttm.resource is NULL

Event History

Aug 15, 2026
CVE Published
via MITRE·05:55 AM
Data Sourced
via MITRE·05:55 AM
Description
Data Sourced
via NVD·06:22 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2026-72359?

CVE-2026-72359 has a risk rating of 27, indicating a significant potential impact.

2

How do I fix CVE-2026-72359?

To resolve CVE-2026-72359, ensure that your Linux kernel is updated to the latest version that includes the fix.

3

What systems are affected by CVE-2026-72359?

CVE-2026-72359 affects the Linux kernel's drm/xe component.

4

What type of vulnerability is CVE-2026-72359?

CVE-2026-72359 is categorized as a Null Pointer Dereference vulnerability.

5

When was CVE-2026-72359 published?

CVE-2026-72359 was published on August 15, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203