Skip to main content
VulnerabilityPublished Updated

CVE-2024-53230: Linux kernel · cpufreq: CPPC: Fix possible null-ptr-deref for cppc_get_cpu_cost()

Source GCVE Database

0
Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 30 Oct 2026, 00:47 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

AI-suggested

A fix has been implemented in the Linux kernel to add a NULL check in cppc_get_cpu_cost(), preventing null pointer dereference. Users should update to the fixed kernel version once available. No other mitigation is indicated.

Description

A null pointer dereference vulnerability was identified and fixed in the Linux kernel's cpufreq subsystem, specifically in the CPPC code path. The function cppc_get_cpu_cost() could dereference a NULL pointer if cpufreq_cpu_get_raw() returned NULL when the CPU was not in the policy's CPU mask. This issue could lead to a denial of service due to kernel crash.

References

Community reviews

Loading reviews…