CVE-2025-37830: cpufreq: scmi: Fix null-ptr-deref in scmi_cpufreq_get_rate()
Published May 8, 2025
·Updated
cpufreq: scmi: Fix null-ptr-deref in scmicpufreqgetrate()
Affected Software
12 affected componentsFixes available
Linux Kernel
Linux Linux kernel>=4.17<5.15.181
Linux Linux kernel>=5.16<6.1.136
Linux Linux kernel>=6.2<6.6.89
Linux Linux kernel>=6.7<6.12.26
Linux Linux kernel>=6.13<6.14.5
Linux Linux kernel=6.15-rc1
Linux Linux kernel=6.15-rc2
Linux Linux kernel=6.15-rc3
Debian Debian Linux=11.0
Microsoft azl3 kernel 6.6.92.2-1
Microsoft azl3 kernel 6.6.85.1-4
Remediation
Event History
May 8, 2025
CVE Published
via MITRE·06:26 AM
Data Sourced
via MITRE·06:26 AM
Description
Data Sourced
via NVD·07:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 11, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2025-37830?
CVE-2025-37830 is considered a moderate severity vulnerability due to the potential for a null pointer dereference.
2
How do I fix CVE-2025-37830?
To fix CVE-2025-37830, update your Linux kernel to a version where the vulnerability has been patched.
3
What systems are affected by CVE-2025-37830?
The vulnerability CVE-2025-37830 affects the Linux kernel, particularly in the cpufreq component.
4
Can CVE-2025-37830 lead to system crashes?
Yes, CVE-2025-37830 could lead to system crashes or unexpected behavior due to a null pointer dereference.
5
Is CVE-2025-37830 an exploit that can be remotely triggered?
CVE-2025-37830 is not typically considered a remote exploit and requires local conditions that could lead to dereferencing a null pointer.