CVE-2024-36024: drm/amd/display: Disable idle reallow as part of command/gpint execution
Published May 30, 2024
·Updated
drm/amd/display: Disable idle reallow as part of command/gpint execution
Affected Software
8 affected componentsFixes available
debian/linux<=5.10.223-1, <=5.10.234-1, <=6.1.129-1, <=6.1.135-1
6.12.25-16.12.27-1
Linux Linux kernel>=4.15<6.8.6
Microsoft cbl2 kernel 5.15.186.1-1
Microsoft azl3 kernel 6.6.104.2-4
Microsoft azl3 kernel 6.6.112.1-2
Microsoft azl3 kernel 6.6.117.1-1
Microsoft azl3 kernel 6.6.96.2-2
Microsoft azl3 kernel 6.6.119.3-1
Remediation
Event History
May 30, 2024
CVE Published
via MITRE·03:04 PM
Data Sourced
via MITRE·03:04 PM
Description
Data Sourced
via NVD·03:15 PM
Description
Data Sourced
via NVD·03:15 PM
RemedySeverityWeaknessAffected Software
Jul 11, 2024
Data Sourced
via Launchpad·07:49 PM
Description
May 5, 2025
Data Sourced
via Ubuntu·12:27 AM
RemedyDescriptionSeverityAffected Software
Sep 4, 2025
Data Sourced
via Microsoft·02:42 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·02:42 AM
Affected Software
Updated
via Microsoft·02:42 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2024-36024?
CVE-2024-36024 has been categorized with a severity that poses a risk due to its potential impact on system performance.
2
How do I fix CVE-2024-36024?
To fix CVE-2024-36024, update the Linux package to version 6.12.12-1 or 6.12.13-1, or ensure your system is running a patched version.
3
Which versions of Linux are affected by CVE-2024-36024?
CVE-2024-36024 affects Linux versions up to 6.1.128, including specific versions like 5.10.223-1 and 5.10.226-1.
4
Does CVE-2024-36024 affect user data security?
CVE-2024-36024 primarily impacts system stability rather than direct user data security.
5
Is there a known workaround for CVE-2024-36024?
Currently, the recommended approach for CVE-2024-36024 is to apply the appropriate software update, as no effective workarounds are documented.