CVE-2025-38535: Linux kernel · phy: tegra: xusb: Fix unbalanced regulator disable in UTMI PHY mode
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ec7f98ff05f0649af0adeb4808c7ba23d6111ef9 : 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 ec7f98ff05f0649af0adeb4808c7ba23d6111ef9, eaa420339658615d26c1cc95cd6cf720b9aebfca, cefc1caee9dd06c69e2d807edc5949b329f52b22 +4
Exploitation evidence
Disclosed: evidence found.
CVE published 16 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: phy: tegra: xusb: Fix unbalanced regulator disable in UTMI PHY mode When transitioning from USB_ROLE_DEVICE to USB_ROLE_NONE, the code assumed that the regulator should be disabled. However, if the regulator is marked as always-on, regulator_is_enabled() continues to return true, leading to an incorrect attempt to disable a regulator which is not enabled. This can result in warnings such as: [ 250.155624] WARNING: CPU: 1 PID: 7326 at drivers/regulator/core.c:3004 _regulator_disable+0xe4/0x1a0 [ 250.155652] unbalanced disables for VIN_SYS_5V0 To fix this, we move the regulator control logic into tegra186_xusb_padctl_id_override() function since it's directly related to the ID override state. The regulator is now only disabled when the role transitions from USB_ROLE_HOST to USB_ROLE_NONE, by checking the VBUS_ID register. This ensures that regulator enable/disable operations are properly balanced and only occur when actually transitioning to/from host mode.
References
- git.kernel.org/stable/c/ceb645ac6ce052609ee5c8f819a80e8881789b04 (opens in a new tab)
- git.kernel.org/stable/c/cdcb0ffd6448f6be898956913a42bd08e59fb2ae (opens in a new tab)
- git.kernel.org/stable/c/1bb85b5c2bd43b687c3d54eb6328917f90dd38fc (opens in a new tab)
- git.kernel.org/stable/c/5367cdeb75cb6c687ca468450bceb2602ab239d8 (opens in a new tab)
- git.kernel.org/stable/c/ec7f98ff05f0649af0adeb4808c7ba23d6111ef9 (opens in a new tab)
- git.kernel.org/stable/c/eaa420339658615d26c1cc95cd6cf720b9aebfca (opens in a new tab)
- git.kernel.org/stable/c/cefc1caee9dd06c69e2d807edc5949b329f52b22 (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)