CVE-2024-41093: drm/amdgpu: avoid using null object of framebuffer
Published Jul 29, 2024
·Updated
drm/amdgpu: avoid using null object of framebuffer
Affected Software
15 affected componentsFixes available
redhat/kernel<5.15.162
5.15.162
redhat/kernel<6.1.97
6.1.97
redhat/kernel<6.6.37
6.6.37
redhat/kernel<6.9.8
6.9.8
redhat/kernel<6.10
6.10
Linux Linux kernel<5.15.162
Linux Linux kernel>=5.16<6.1.97
Linux Linux kernel>=6.2<6.6.37
Linux Linux kernel>=6.7<6.9.8
debian/linux<=5.10.223-1, <=5.10.234-1
6.1.129-16.1.135-16.12.25-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1
IBM Security Verify Governance<=ISVG 10.0.2
IBM Security Verify Governance - Identity Manager virtual appliance component<=ISVG 10.0.2
Microsoft azl3 kernel 6.6.43.1-7
Microsoft azl3 kernel 6.6.35.1-5
Remediation
Event History
Jul 29, 2024
CVE Published
via MITRE·03:48 PM
Data Sourced
via MITRE·03:48 PM
Description
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Aug 16, 2024
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
May 13, 2025
Data Sourced
via Ubuntu·12:34 AM
RemedyDescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2024-41093?
CVE-2024-41093 has been classified as a medium-severity vulnerability in the Linux kernel.
2
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.
3
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.
4
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.
5
Who is affected by CVE-2024-41093?
Users and administrators running the affected versions of the Linux kernel are susceptible to CVE-2024-41093.