CVE-2024-38573: cppc_cpufreq: Fix possible null pointer dereference
In the Linux kernel, the following vulnerability has been resolved:
cppc_cpufreq: Fix possible null pointer dereference
cppc_cpufreq_get_rate() and hisi_cppc_cpufreq_get_rate() can be called from
different places with various parameters. So cpufreq_cpu_get() can return
null as 'policy' in some circumstances.
Fix this bug by adding null return check.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash affected systems when CPU frequency policy lookup unexpectedly returns null in CPPC CPU frequency code. The known impact is availability loss, not data theft or privilege escalation. Treat it as important for Linux fleets where uptime matters, especially systems using CPPC-related CPU frequency handling.
Executive priority
Patch through normal high-priority kernel maintenance, accelerated for exposed or uptime-sensitive Linux systems. Current evidence supports denial-of-service risk, not compromise of confidentiality or integrity. No active exploitation is shown in the provided sources.
Technical view
CVE-2024-38573 is a CWE-476 null pointer dereference in Linux kernel cppc_cpufreq_get_rate() and hisi_cppc_cpufreq_get_rate(). cpufreq_cpu_get() may return a null policy in some circumstances, and the kernel fix adds a null return check. CVSS is 7.5 with availability-only impact.
Likely exposure
Exposure is limited to affected Linux kernel versions and configurations using the relevant CPPC CPU frequency driver paths. The bundle lists affected Linux versions including 5.11, 5.15.161, 6.1.93, 6.6.33, 6.8.12, 6.9.3, and 6.10, but does not map distributions or architectures.
Exploitation context
The source bundle does not show CISA KEV listing or public active exploitation. The CVSS vector states network, low complexity, no privileges, and no user interaction, but the provided sources do not describe exploit mechanics or a public proof of concept.
Researcher notes
The record is sparse: it names the faulty functions and fix pattern but not triggering conditions, platforms, or distribution status. Analysis should focus on kernel version lineage, CPPC driver reachability, and whether downstream vendor kernels have backported the null policy check.
Mitigation direction
Check the running kernel against vendor advisories and fixed stable commits.
Prioritize kernel updates on systems where availability is business-critical.
Use distribution-provided kernel packages rather than manually cherry-picking when possible.
Review whether affected systems use CPPC CPU frequency functionality.
Monitor vendor security notices for backports and distribution-specific status.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and cloud images.
Confirm whether vendor kernels include the referenced stable fixes.
Check fleet telemetry for unexpected kernel crashes or availability events.
Verify patched systems boot the updated kernel after maintenance.
Document exceptions where vendor guidance is unavailable or pending.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-476: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-476 · source CWE mapping
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.