CVE-2024-41093: drm/amdgpu: avoid using null object of framebuffer
drm/amdgpu: avoid using null object of framebuffer
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/kernelto a version that resolves this vulnerability.Fixed in 5.15.162 - Upgrade
Upgrade
redhat/kernelto a version that resolves this vulnerability.Fixed in 6.1.97 - Upgrade
Upgrade
redhat/kernelto a version that resolves this vulnerability.Fixed in 6.6.37 - Upgrade
Upgrade
redhat/kernelto a version that resolves this vulnerability.Fixed in 6.9.8 - Upgrade
Upgrade
redhat/kernelto a version that resolves this vulnerability.Fixed in 6.10 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.98-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.9.8-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-41093?
CVE-2024-41093 has been classified as a medium-severity vulnerability in the Linux kernel.
How do I fix CVE-2024-41093?
To fix CVE-2024-41093, upgrade to the specified Linux kernel versions 5.15.162, 6.1.97, 6.6.37, 6.9.8, 6.10, or the relevant Debian packages listed.
Which Linux kernel versions are affected by CVE-2024-41093?
CVE-2024-41093 affects Linux kernel versions prior to 5.15.162 and versions between 6.1.97 and 6.6.37.
Is there a workaround for CVE-2024-41093?
There is no known workaround for CVE-2024-41093, and updating the kernel is the recommended action.
Who is affected by CVE-2024-41093?
Users and administrators running the affected versions of the Linux kernel are susceptible to CVE-2024-41093.