CVE-2024-46720: drm/amdgpu: fix dereference after null check
Published Sep 18, 2024
·Updated
drm/amdgpu: fix dereference after null check
Affected Software
7 affected componentsFixes available
Linux Linux kernel<6.1.109
Linux Linux kernel>=6.2<6.6.50
Linux Linux kernel>=6.7<6.10.9
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
Microsoft azl3 kernel 6.6.47.1-1
Microsoft azl3 kernel 6.6.51.1-5
Remediation
Event History
Sep 18, 2024
CVE Published
via MITRE·06:32 AM
Data Sourced
via MITRE·06:32 AM
Description
Data Sourced
via NVD·07:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Oct 16, 2024
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·07:00 AM
SeverityAffected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Apr 27, 2025
Data Sourced
via Ubuntu·08:37 PM
RemedyDescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2024-46720?
CVE-2024-46720 has a medium severity rating due to potential data exposure risks.
2
How do I fix CVE-2024-46720?
To fix CVE-2024-46720, update your Linux kernel to the patched versions: 6.1.123-1, 6.1.119-1, 6.12.9-1, or 6.12.10-1.
3
Which Linux distributions are affected by CVE-2024-46720?
CVE-2024-46720 affects various Debian Linux kernel packages and versions prior to the patched versions mentioned.
4
What is the impact of CVE-2024-46720 on system stability?
CVE-2024-46720 can lead to potential instability or crashes in systems utilizing the vulnerable kernel versions.
5
Is CVE-2024-46720 exploitable remotely?
CVE-2024-46720 is not confirmed to be remotely exploitable but can pose risks if an attacker has local access to the system.