drm/xe/gsc: Fix double-free of managed BO in error path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/xe/gsc: Fix double-free of managed BO in error path
The error path in xe_gsc_init_post_hwconfig() 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 71d61e3e299a17139e47f980a4d6f425b2c59bf7)
From the CVE record · Linux
The Linux kernel’s drm/xe/gsc initialization error path explicitly frees a managed buffer that is also registered for automatic cleanup, causing a double-free when cleanup runs during probe failure. The input does not establish whether an attacker can trigger the failure or specify network access, authentication, or user-interaction requirements.
Engineers running Linux kernels with the affected drm/xe/gsc code should check their deployments; affected versions are not specified.