CVE-2026-68273
CVE CVE-2026-68273EUVD EUVD-2026-55374Published 2026-08-10T12:01:48.000Z
What the advisory describes
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)
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 6607901fce79959130db485e7549dacaaeef034e; 6.1; patch: 6.12.103; 79610d3041338dc1ef554d6fd8b3b3e23be527f5 <e06c39cc1c48dca68a5ffd971c23025a52d46634; 79610d3041338dc1ef554d6fd8b3b3e23be527f5 <23a8726e1d7597fe7c9a59d5dc42ba8b7d345b8a; 79610d3041338dc1ef554d6fd8b3b3e23be527f5 <9f9c88eb298c54348be3ca4087f4f4c615065b87; 79610d3041338dc1ef554d6fd8b3b3e23be527f5 <c1dc4ccb82c9e56325d8e7514ca4c90bd1efb351; patch: 7.1.6; 6.0.7 <6.1; patch: 0; patch: 6.18.44; patch: 7.2-rc1
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.