drm/xe/client: fix deadlock in show_meminfo()
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/client: fix deadlock in show_meminfo()
There is a real deadlock as well as sleeping in atomic() bug in here, if the bo put happens to be the last ref, since bo destruction wants to grab the same spinlock and sleeping locks. Fix that by dropping the ref using xe_bo_put_deferred(), and moving the final commit outside of the lock. Dropping the lock around the put is tricky since the bo can go out of scope and delete itself from the list, making it difficult to navigate to the next list entry.
(cherry picked from commit 0083b8e6f11d7662283a267d4ce7c966812ffd8a)
From the CVE record · Linux
The Linux kernel’s drm/xe/client show_meminfo() can deadlock or sleep while holding a spinlock if releasing a buffer object drops its last reference. The input does not specify how an attacker could trigger this, what access they would need, or whether user interaction is required.
Engineers running Linux kernels with the affected drm/xe/client code should check their deployments; affected versions are not specified.