CVE-2024-46851 Details
Description
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Avoid race between dcn10_set_drr() and dc_state_destruct() dc_state_destruct() nulls the resource context of the DC state. The pipe context passed to dcn10_set_drr() is a member of this resource context. If dc_state_destruct() is called parallel to the IRQ processing (which calls dcn10_set_drr() at some point), we can end up using already nulled function callback fields of struct stream_resource. The logic in dcn10_set_drr() 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)
A race condition vulnerability has been addressed in the Linux kernel's AMD display driver. The issue arises in the 'dcn10_set_drr()' function, which is part of the display pipeline context. When 'dc_state_destruct()' is called, it nullifies the resource context, including the timing generator used by 'dcn10_set_drr()'. If this nulling occurs simultaneously with the processing of interrupts that trigger 'dcn10_set_drr()', the function may attempt to access already nullified callback fields, leading to undefined behavior. Although 'dcn10_set_drr()' includes a check to prevent this by verifying that the timing generator is not NULL, a race condition can still occur if the nulling happens right after this check and before the function accesses the timing generator again. This vulnerability has been fixed by modifying 'dcn10_set_drr()' to first copy the timing generator reference to a local variable, ensuring that the function operates on a valid reference throughout its execution. This change prevents the race condition while maintaining the integrity of the resource management.
Users can upgrade to the latest version of the Linux kernel where this vulnerability has been addressed. The specific commit containing the fix is available in the Linux kernel stable tree.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Sep 29, 2024References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/a7aeb03888b92304e2fc7d4d1c242f54a312561b | kernel.org | Patch |
| https://git.kernel.org/stable/c/b6ce047a81f508f5c60756db8dfb5ff486e4dad0 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-476 | NULL Pointer Dereference | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.7, < 6.10.11 6.11 rc1 6.11 rc2 6.11 rc3 6.11 rc4 6.11 rc5 6.11 rc6 6.11 rc7 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Oct 4, 2024 | Initial Analysis | [email protected] |
| Sep 27, 2024 | New CVE Received | kernel.org |