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-38668regulator: core: fix NULL dereference on unbind due to stale coupling data

Description

In the Linux kernel, the following vulnerability has been resolved: regulator: core: fix NULL dereference on unbind due to stale coupling data Failing to reset coupling_desc.n_coupled after freeing coupled_rdevs can lead to NULL pointer dereference when regulators are accessed post-unbind. This can happen during runtime PM or other regulator operations that rely on coupling metadata. For example, on ridesx4, unbinding the 'reg-dummy' platform device triggers a panic in regulator_lock_recursive() due to stale coupling state. Ensure n_coupled is set to 0 to prevent access to invalid pointers.

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 15 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-38668, 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 92% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
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 d8ca7d184b33af7913c244900df77c6cad6a5590 – < 7574892e259bbb16262ebfb4b65a2054a5e03a49
    • affected d8ca7d184b33af7913c244900df77c6cad6a5590 – < 6c49eac796681e250e34156bafb643930310bd4a
    • affected d8ca7d184b33af7913c244900df77c6cad6a5590 – < ca9bef9ba1a6be640c87bf802d2e9e696021576a
    • affected d8ca7d184b33af7913c244900df77c6cad6a5590 – < 800a2cfb2df7f96b3fb48910fc595e0215f6b019
    • affected d8ca7d184b33af7913c244900df77c6cad6a5590 – < 233d3c54c9620e95193923859ea1d0b0f5d748ca
    • affected d8ca7d184b33af7913c244900df77c6cad6a5590 – < 5d4261dbb3335221fd9c6e69f909ba79ee6663a7
    • affected d8ca7d184b33af7913c244900df77c6cad6a5590 – < d7e59c5fd7a0f5e16e75a30a89ea2c4ab88612b8
    • affected d8ca7d184b33af7913c244900df77c6cad6a5590 – < ca46946a482238b0cdea459fb82fc837fb36260e
  • Linux · Linux

    • affected 5.3
    • unaffected < 5.3
    • unaffected 5.4.297 – ≤ 5.4.*
    • unaffected 5.10.241 – ≤ 5.10.*
    • unaffected 5.15.190 – ≤ 5.15.*
    • unaffected 6.1.148 – ≤ 6.1.*
    • unaffected 6.6.101 – ≤ 6.6.*
    • unaffected 6.12.41 – ≤ 6.12.*
    • unaffected 6.15.9 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .