drm/xe/oa: Fix potential UAF in xe_oa_add_config_ioctl()
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.12.646.18.46.19In the Linux kernel, the following vulnerability has been resolved:
drm/xe/oa: Fix potential UAF in xe_oa_add_config_ioctl()
In xe_oa_add_config_ioctl(), we accessed oa_config->id after dropping metrics_lock. Since this lock protects the lifetime of oa_config, an attacker could guess the id and call xe_oa_remove_config_ioctl() with perfect timing, freeing oa_config before we dereference it, leading to a potential use-after-free.
Fix this by caching the id in a local variable while holding the lock.
v2: (Matt A) - Dropped mutex_unlock(&oa->metrics_lock) ordering change from xe_oa_remove_config_ioctl()
(cherry picked from commit 28aeaed130e8e587fd1b73b6d66ca41ccc5a1a31)
From the CVE record · Linux
The Linux kernel’s xe_oa_add_config_ioctl() can access a configuration after dropping the lock that protects its lifetime. An attacker able to call the configuration ioctls could guess its ID and time a removal call to free it before that access, causing a potential use-after-free. The input does not specify authentication requirements or whether user interaction is needed.
Engineers running Linux kernels with the drm/xe/oa component should check their vendor advisory for affected versions; none are specified here.