Linux Kernel up to 6.1.147/6.6.100/6.12.40/6.15.8 regulator regulator_lock_recursive null pointer dereference

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.5$0-$5k0.00

Summaryinfo

A vulnerability classified as critical was found in Linux Kernel up to 6.1.147/6.6.100/6.12.40/6.15.8. Affected by this vulnerability is the function regulator_lock_recursive of the component regulator. The manipulation results in null pointer dereference. This vulnerability is known as CVE-2025-38668. No exploit is available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.1.147/6.6.100/6.12.40/6.15.8. It has been classified as critical. Affected is the function regulator_lock_recursive of the component regulator. The manipulation with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on availability. CVE summarizes:

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.

The advisory is available at git.kernel.org. This vulnerability is traded as CVE-2025-38668 since 04/16/2025. Technical details are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 260271 (Linux Distros Unpatched Vulnerability : CVE-2025-38668), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.1.148, 6.6.101, 6.12.41 or 6.15.9 eliminates this vulnerability. Applying the patch 800a2cfb2df7f96b3fb48910fc595e0215f6b019/233d3c54c9620e95193923859ea1d0b0f5d748ca/5d4261dbb3335221fd9c6e69f909ba79ee6663a7/d7e59c5fd7a0f5e16e75a30a89ea2c4ab88612b8/ca46946a482238b0cdea459fb82fc837fb36260e is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (260271) and CERT Bund (WID-SEC-2025-1898). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Affected

  • Debian Linux
  • Google Cloud Platform
  • Amazon Linux 2
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • NetApp AFF
  • NetApp ActiveIQ Unified Manager
  • SUSE openSUSE
  • Dell Avamar
  • NetApp FAS
  • Open Source Linux Kernel
  • Dell NetWorker
  • Dell Secure Connect Gateway

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.6
VulDB Meta Temp Score: 5.5

VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Null pointer dereference
CWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 260271
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-38668

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.1.148/6.6.101/6.12.41/6.15.9
Patch: 800a2cfb2df7f96b3fb48910fc595e0215f6b019/233d3c54c9620e95193923859ea1d0b0f5d748ca/5d4261dbb3335221fd9c6e69f909ba79ee6663a7/d7e59c5fd7a0f5e16e75a30a89ea2c4ab88612b8/ca46946a482238b0cdea459fb82fc837fb36260e

Timelineinfo

04/16/2025 CVE reserved
08/22/2025 +128 days Advisory disclosed
08/22/2025 +0 days VulDB entry created
02/14/2026 +176 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-38668 (🔒)
GCVE (CVE): GCVE-0-2025-38668
GCVE (VulDB): GCVE-100-321090
CERT Bund: WID-SEC-2025-1898 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Entryinfo

Created: 08/22/2025 23:32
Updated: 02/14/2026 07:44
Changes: 08/22/2025 23:32 (59), 09/02/2025 16:51 (2), 09/22/2025 03:58 (7), 10/18/2025 06:58 (1), 10/26/2025 12:28 (1), 12/13/2025 14:16 (1), 01/09/2026 06:48 (11), 02/14/2026 07:44 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!