CVE-2025-38668: Linux kernel · regulator: core: fix NULL dereference on unbind due to stale coupling data
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d7e59c5fd7a0f5e16e75a30a89ea2c4ab88612b8 : update Linux kernel when convenient.
Data as of 5 Nov 2026, 23:23 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-05.
- Patch
- Available – fixed in d7e59c5fd7a0f5e16e75a30a89ea2c4ab88612b8, ca46946a482238b0cdea459fb82fc837fb36260e, ca9bef9ba1a6be640c87bf802d2e9e696021576a +5
Exploitation evidence
Disclosed: evidence found.
CVE published 22 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 5 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
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.
References
- git.kernel.org/stable/c/7574892e259bbb16262ebfb4b65a2054a5e03a49 (opens in a new tab)
- git.kernel.org/stable/c/6c49eac796681e250e34156bafb643930310bd4a (opens in a new tab)
- git.kernel.org/stable/c/ca9bef9ba1a6be640c87bf802d2e9e696021576a (opens in a new tab)
- git.kernel.org/stable/c/800a2cfb2df7f96b3fb48910fc595e0215f6b019 (opens in a new tab)
- git.kernel.org/stable/c/233d3c54c9620e95193923859ea1d0b0f5d748ca (opens in a new tab)
- git.kernel.org/stable/c/5d4261dbb3335221fd9c6e69f909ba79ee6663a7 (opens in a new tab)
- git.kernel.org/stable/c/d7e59c5fd7a0f5e16e75a30a89ea2c4ab88612b8 (opens in a new tab)
- git.kernel.org/stable/c/ca46946a482238b0cdea459fb82fc837fb36260e (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/10/msg00007.html (opens in a new tab)