Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-38610powercap: dtpm_cpu: Fix NULL pointer dereference in get_pd_power_uw()

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 ]

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 9 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38610, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected eb82bace893169b319c563b7f813c58a0a5a9f76 – < 27914f2b795e2b58e9506f281dcdd98fef09d3c2
    • affected eb82bace893169b319c563b7f813c58a0a5a9f76 – < c6ec27091cf5ac05094c1fe3a6ce914cf711a37c
    • affected eb82bace893169b319c563b7f813c58a0a5a9f76 – < 8374ac7d69a57d737e701a851ffe980a0d27d3ad
    • affected eb82bace893169b319c563b7f813c58a0a5a9f76 – < 27e0318f0ea69fcfa32228847debc384ade14578
    • affected eb82bace893169b319c563b7f813c58a0a5a9f76 – < 2fd001a0075ac01dc64a28a8e21226b3d989a91d
    • affected eb82bace893169b319c563b7f813c58a0a5a9f76 – < 46dc57406887dd02565cb264224194a6776d882b
  • Linux · Linux

    • affected 5.16
    • unaffected < 5.16
    • unaffected 6.1.148 – ≤ 6.1.*
    • unaffected 6.6.102 – ≤ 6.6.*
    • unaffected 6.12.42 – ≤ 6.12.*
    • unaffected 6.15.10 – ≤ 6.15.*
    • unaffected 6.16.1 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38610 badge
[![CVE-2025-38610](https://cveledger.app/badge/CVE-2025-38610.svg)](https://cveledger.app/cve/CVE-2025-38610)

Record last updated .