Linux kernel runtime power reference underflow in amdgpu debugfs reads
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9eee152aab56d374edb9ad21b3db05f5cdda2fe6 · < 652b1f26125fe48aed5f4944698a85b457eef491| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: don't drop the runtime PM reference twice in amdgpu_gpr
amdgpu_debugfs_gpr_read() drops its runtime PM reference right after reading the wave registers. When copying them to userspace fails, it jumps to the err label, which drops the reference a second time. A read into a bad buffer on Navi31 either steals a reference somebody else holds (power/runtime_usage goes from 1 to 0) or underflows the count:
amdgpu 0000:03:00.0: Runtime PM usage count underflow!
The registers are already in the kernel buffer at that point, so finish the hardware access first and copy the buffer with a single copy_to_user() instead of the put_user() loop with its own error path.
(cherry picked from commit 31035bbd74f7c3e10c163db875b8e67f8b50ee6a)
From the CVE record · Linux
The Linux kernel’s amdgpu debugfs GPR read path can drop a runtime power-management reference twice when copying wave registers to a userspace buffer fails. A local caller able to read this debugfs entry with a bad buffer can cause the usage count to underflow or consume a reference held elsewhere.
Teams running Linux kernels with the affected amdgpu debugfs GPR read path should check their systems; affected versions were not specified.