CVE-2024-46851: drm/amd/display: Avoid race between dcn10_set_drr() and dc_state_destruct()
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Avoid race between dcn10setdrr() and dcstatedestruct()
dcstatedestruct() nulls the resource context of the DC state. The pipe context passed to dcn10setdrr() is a member of this resource context.
If dcstatedestruct() is called parallel to the IRQ processing (which calls dcn10setdrr() at some point), we can end up using already nulled function callback fields of struct streamresource.
The logic in dcn10setdrr() already tries to avoid this, by checking tg against NULL. But if the nulling happens exactly after the NULL check and before the next access, then we get a race.
Avoid this by copying tg first to a local variable, and then use this variable for all the operations. This should work, as long as nobody frees the resource pool where the timing generators live.
(cherry picked from commit a3cc326a43bdc48fbdf53443e1027a03e309b643)
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-46851?
CVE-2024-46851 is classified as a moderate severity vulnerability in the Linux kernel.
How do I fix CVE-2024-46851?
To fix CVE-2024-46851, update to a patched version of the Linux kernel such as 5.10.223-1 or later.
What systems are affected by CVE-2024-46851?
CVE-2024-46851 affects Linux kernel versions from 6.7 to 6.10.11 and specifically 6.11 release candidates.
What is the impact of CVE-2024-46851?
The impact of CVE-2024-46851 includes potential race conditions that could be exploited to compromise system stability.
Are there any workarounds for CVE-2024-46851?
There are no recommended workarounds for CVE-2024-46851; the best solution is to apply the appropriate kernel updates.