drm/amdgpu: Fix context pstate override handling
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.1, 6.6.160, 6.12.103, 6.18.44, 7.1.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix context pstate override handling There are several problems in the context pstate handling code. The most serious ones are potential use-after-free and NULL pointer dereferences at context initialization time. Both are due amdgpu_ctx_init() not holding the adev->pm.stable_pstate_ctx_lock, which is otherwise used from both sysfs and the context code itself for modifying and clearing the stored context pointer. Second issue is that context fini can trample over the pstate configuration set via sysfs. This is due the restore state (ctx->stable_pstate) being saved at context init time, and not if, or when the context actually changes the pstate. As the context exits it will therefore incorrectly restore to what was set before the sysfs override was requested. The simplest fix is to drastically simplify how the state is tracked, by clearly defining the points at which pstate ownership is taken and released, and to handle all transitions under the correct lock. Instead of at context init time, the previous state is saved only at the point the context overrides the current state, and is restored on context exit only if the context is still the owner of the current override state. (cherry picked from commit 1b5e413713c0a93bc1818394d0ce49aaad21bd27)
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 79610d3041338dc1ef554d6fd8b3b3e23be527f5 · fixed in 3531910845165dcf1a213267199ccc97e03cd58a; From 79610d3041338dc1ef554d6fd8b3b3e23be527f5 · fixed in 23a8726e1d7597fe7c9a59d5dc42ba8b7d345b8a; From 79610d3041338dc1ef554d6fd8b3b3e23be527f5 · fixed in e06c39cc1c48dca68a5ffd971c23025a52d46634; From 79610d3041338dc1ef554d6fd8b3b3e23be527f5 · fixed in 9f9c88eb298c54348be3ca4087f4f4c615065b87; From 79610d3041338dc1ef554d6fd8b3b3e23be527f5 · fixed in c1dc4ccb82c9e56325d8e7514ca4c90bd1efb351; From 6.0.7 · fixed in 6.1
- Linux Linux
6.1
- KernelLinux
From 6.1.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.103; From 6.13.0 · fixed in 6.18.44; From 6.19.0 · fixed in 7.1.6