CVE-2025-38705: drm/amd/pm: fix null pointer access
Published Sep 4, 2025
·Updated
drm/amd/pm: fix null pointer access
Affected Software
11 affected components
Linux Kernel
Microsoft azl3 kernel 6.6.96.2-2
Microsoft azl3 kernel 6.6.96.2-1
Linux Linux kernel<6.12.43
Linux Linux kernel>=6.13<6.15.11
Linux Linux kernel>=6.16<6.16.2
Microsoft cbl2 kernel 5.15.186.1-1
Microsoft azl3 kernel 6.6.112.1-2
Microsoft azl3 kernel 6.6.104.2-4
Microsoft azl3 kernel 6.6.117.1-1
Microsoft azl3 kernel 6.6.119.3-1
Event History
Sep 4, 2025
CVE Published
via MITRE·03:32 PM
Data Sourced
via MITRE·03:32 PM
Description
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Sep 6, 2025
Data Sourced
via Microsoft·01:08 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·01:08 AM
Affected Software
Updated
via Microsoft·01:08 AM
SeverityAffected Software
Updated
via Microsoft·08:08 AM
DescriptionWeakness
Updated
via Microsoft·08:08 AM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2025-38705?
CVE-2025-38705 has been classified as a moderate severity vulnerability due to the potential for null pointer dereference.
2
How do I fix CVE-2025-38705?
To mitigate CVE-2025-38705, ensure that your Linux kernel is updated to the latest stable version that resolves this issue.
3
What systems are affected by CVE-2025-38705?
CVE-2025-38705 affects the Linux kernel, specifically related to drm/amd/pm subsystems.
4
What happens if CVE-2025-38705 is exploited?
Exploitation of CVE-2025-38705 may lead to a null pointer dereference, which can result in system crashes or instability.
5
Is there a workaround for CVE-2025-38705?
Currently, implementing input validation to avoid writing strings without delimiters to the affected sysfs entries could serve as a temporary workaround for CVE-2025-38705.