CVE-2025-38610: debian linux Null Dereference — Fix

Description

In the Linux kernel, the following vulnerability has been resolved: powercap: dtpm_cpu: Fix NULL pointer dereference in get_pd_power_uw() The get_pd_power_uw() function can crash with a NULL pointer dereference when em_cpu_get() returns NULL. This occurs when a CPU becomes impossible during runtime, causing get_cpu_device() to return NULL, which propagates through em_cpu_get() and leads to a crash when em_span_cpus() dereferences the NULL pointer. Add a NULL check after em_cpu_get() and return 0 if unavailable, matching the existing fallback behavior in __dtpm_cpu_setup(). [ rjw: Drop an excess empty code line ]

Is your site exposed to CVE-2025-38610?

Run a free security scan — no signup, results in seconds.

CVSS v3.1 Score

5.5

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Weakness Type (CWE)

CWE-476 CWE-476

Affected Products

Vendor	Product	Versions
linux	linux_kernel	5.16 — 6.1.148
linux	linux_kernel	6.2 — 6.6.102
linux	linux_kernel	6.7 — 6.12.42
linux	linux_kernel	6.13 — 6.15.10
linux	linux_kernel	6.16 — 6.16.1
debian	debian_linux	All

References

Advisories & Patches

https://git.kernel.org/stable/c/27914f2b795e2b58e9506f281dcdd98fef09d3c2 https://git.kernel.org/stable/c/27e0318f0ea69fcfa32228847debc384ade14578 https://git.kernel.org/stable/c/2fd001a0075ac01dc64a28a8e21226b3d989a91d https://git.kernel.org/stable/c/46dc57406887dd02565cb264224194a6776d882b https://git.kernel.org/stable/c/8374ac7d69a57d737e701a851ffe980a0d27d3ad https://git.kernel.org/stable/c/c6ec27091cf5ac05094c1fe3a6ce914cf711a37c

Other References

https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html

Frequently Asked Questions

What is CVE-2025-38610? +

In the Linux kernel, the following vulnerability has been resolved: powercap: dtpm_cpu: Fix NULL pointer dereference in get_pd_power_uw() The get_pd_power_uw() function can crash with a NULL pointer dereference when em_cpu_get() returns NULL. This occurs when a CPU becomes impossible during runtime, causing get_cpu_device() to return NULL, which propagates through em_cpu_get() and leads to a crash when em_span_cpus() dereferences the NULL pointer. Add a NULL check after em_cpu_get() and return 0 if unavailable, matching the existing fallback behavior in __dtpm_cpu_setup(). [ rjw: Drop an excess empty code line ] It has a CVSS v3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2025-38610? +

CVE-2025-38610 has a CVSS v3.1 score of 5.5 out of 10, rated MEDIUM. This is a medium-severity vulnerability that should be remediated as part of regular maintenance.

What products are affected by CVE-2025-38610? +

CVE-2025-38610 affects products from debian, linux, specifically: debian_linux, linux_kernel. Check the affected products table above for specific version ranges.

How do I check if I'm vulnerable to CVE-2025-38610? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.

Related Vulnerabilities

CVE-2026-8479

IEC 60870-5-104 used in bidirectional mode in RTU500 is vulnerable for a NULL pointer dereferencing, if a specially crafted sequence …

CVE-2025-24031

PAM-PKCS#11 is a Linux-PAM login module that allows a X.509 certificate based user login. In versions 0.6.12 and prior, the …

CVE-2025-31115

XZ Utils provide a general-purpose data-compression library plus command-line tools. In XZ Utils 5.3.3alpha to 5.8.0, the multithreaded .xz decoder …

CVE-2025-0121

A null pointer dereference vulnerability in the Palo Alto Networks Cortex® XDR agent on Windows devices allows a low-privileged local …

CVE-2023-45925

GNU Midnight Commander 4.8.29-146-g299d9a2fb was discovered to contain a NULL pointer dereference via the function x_error_handler() at tty/x11conn.c. NOTE: this …

CVE-2025-6398

A null pointer dereference vulnerability exists in the IOMap64.sys driver of ASUS AI Suite 3. The vulnerability can be triggered …

CVE-2025-38610