CVE-2026-72361

Received Received - Intake

Double-free in Linux Kernel's DRM/XE hw_engine

Publication date: 2026-08-15

Last updated on: 2026-08-17

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: drm/xe/hw_engine: Fix double-free of managed BO in error path The error path in hw_engine_init() explicitly frees a BO allocated with xe_managed_bo_create_pin_map() via xe_bo_unpin_map_no_vm(). Since the managed BO already has a devm cleanup action registered, this causes a double-free when devm unwinds during probe failure. Remove the explicit free and let devm handle it, consistent with all other xe_managed_bo_create_pin_map() callers. (cherry picked from commit e459a3bdeb117be496d7f229e2ea1f6c9fe4080b)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-15

Last Modified

2026-08-17

Generated

2026-09-04

AI Q&A

2026-08-15

EPSS Evaluated

2026-09-03

NVD

CVE-2026-72361

EUVD

EUVD-2026-59260

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This is a double-free vulnerability in the Linux kernel's drm/xe/hw_engine component. It occurs when an error path in the hw_engine_init() function explicitly frees a buffer object (BO) that was allocated with xe_managed_bo_create_pin_map(). The BO already has a cleanup action registered with the device resource manager (devm), so explicitly freeing it causes a double-free when devm attempts to clean up during probe failure.

Detection Guidance

This vulnerability is specific to the Linux kernel's drm/xe/hw_engine component and involves a double-free issue in error paths. Detection requires checking kernel logs for probe failures or crashes related to the xe driver. Commands like dmesg | grep xe or journalctl -k | grep xe may help identify errors. Ensure your kernel version is updated to a patched release.

Impact Analysis

This vulnerability could lead to kernel memory corruption or crashes if the affected error path is triggered during device probe. This may cause system instability, denial of service, or potential privilege escalation depending on the system configuration and kernel version.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards as it is a low-level kernel memory management issue unrelated to data protection or privacy controls.

Mitigation Strategies

Update your Linux kernel to the latest stable version that includes the fix for CVE-2026-72361. If immediate patching is not possible, consider disabling the xe driver module (rmmod xe) as a temporary workaround. Monitor kernel logs for any xe-related errors post-update.

Hi! I’m here to help you understand CVE-2026-72361. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70