First published: Wed Dec 04 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Handle dml allocation failure to avoid crash [Why] In the case where a dml allocation fails for any reason, the current state's dml contexts would no longer be valid. Then subsequent calls dc_state_copy_internal would shallow copy invalid memory and if the new state was released, a double free would occur. [How] Reset dml pointers in new_state to NULL and avoid invalid pointer (cherry picked from commit bcafdc61529a48f6f06355d78eb41b3aeda5296c)
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | <6.11.10 | |
Linux Kernel | =6.12-rc1 | |
Linux Kernel | =6.12-rc2 | |
Linux Kernel | =6.12-rc3 | |
Linux Kernel | =6.12-rc4 | |
Linux Kernel | =6.12-rc5 | |
Linux Kernel | =6.12-rc6 | |
Linux Kernel | =6.12-rc7 | |
debian/linux | <=5.10.223-1<=5.10.234-1<=6.1.129-1<=6.1.135-1 | 6.12.25-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-53133 has a moderate severity level due to the potential for crashes in the Linux kernel.
To fix CVE-2024-53133, upgrade to the latest stable version of the Linux kernel that addresses this vulnerability.
CVE-2024-53133 affects Linux kernel versions prior to 6.12-rc1 and all 6.12 release candidates up to 6.12-rc7.
The impact of CVE-2024-53133 is that it can lead to system crashes due to invalid DML contexts after allocation failures.
CVE-2024-53133 is present in affected versions of the Linux kernel but may not be in all distributions if patched.