drm/i915: fix race condition UAF in i915_perf_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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/i915: fix race condition UAF in i915_perf_add_config_ioctl
Userspace can guess the id value and try to race oa_config object creation with config remove, resulting in a use-after-free if we dereference the object after unlocking the metrics_lock. For that reason, unlocking the metrics_lock must be done after we are done dereferencing the object.
[tursulin: Manually added stable tag.] (cherry picked from commit 49f6f6483b652108bcb73accd0204a464b922395)
From the CVE record · Linux
The Linux kernel's drm/i915 performance configuration code has a race condition in i915_perf_add_config_ioctl. A local userspace attacker can guess a configuration ID and race its creation against removal, causing a use-after-free when the object is dereferenced after metrics_lock is released.
Engineers running Linux kernels with the affected drm/i915 code should check their systems; affected versions were not specified.