drm/xe/oa: Fix exec_queue leak on width check in stream open
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 |
|
|
6.18.347.0.117.1In the Linux kernel, the following vulnerability has been resolved:
drm/xe/oa: Fix exec_queue leak on width check in stream open
In xe_oa_stream_open_ioctl(), when param.exec_q->width > 1 the function returns -EOPNOTSUPP directly, skipping the existing err_exec_q cleanup path. The exec_queue reference obtained by xe_exec_queue_lookup() is leaked.
The exec queue holds a reference on the xe_file, which is only dropped during queue teardown. The leaked lookup ref is not on the file's exec_queue xarray, so file close cannot release it. This keeps both the exec queue and the file private state pinned indefinitely.
Jump to err_exec_q instead of returning directly so the reference is released.
(cherry picked from commit 339fa0be9e4a5d69fa47e91f4a36574224fb478f)
From the CVE record · Linux
The Linux kernel's xe OA stream-open ioctl leaks an exec queue reference when the queue width is greater than one. A local caller able to invoke the ioctl can keep the exec queue and file-private state pinned indefinitely; no additional user interaction is described.
Check Linux kernel deployments using the xe driver; affected versions are not specified.