CVE-2025-38535 json
phy: tegra: xusb: Fix unbalanced regulator disable in UTMI PHY mode
published 2025-08-16 14 mo ago modified 2026-11-05 3 d ago also EUVD-2025-26110
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.10.241, 5.15.190, 6.1.147, 6.6.100, 6.12.40, 6.15.8, 6.16
- linux Debian 12 6.1.147-1
- linux Debian 13 6.12.41-1
- linux Debian 14 6.16.3-1
debian advisories DEBIAN-CVE-2025-38535
- linux Ubuntu 22.04 LTS 5.15.0-163.173
- linux Ubuntu 24.04 LTS 6.8.0-100.100
- linux-aws Ubuntu 22.04 LTS 5.15.0-1097.104
- linux-aws Ubuntu 24.04 LTS 6.8.0-1046.49
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1097.106
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1047.50
- linux-gke Ubuntu 22.04 LTS 5.15.0-1093.99
- linux-gke Ubuntu 24.04 LTS 6.8.0-1043.48
ubuntu advisories UBUNTU-CVE-2025-38535
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-rt Linux Micro 6.2 6.12.0-160000.26.1
- kernel-64kb SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.26.1
- kernel-source SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.26.1
- kernel-default SLES 16.0, SLE High Availability Extension 16.0, Linux Micro 6.2 +1 more 6.12.0-160000.26.1
- kernel-default-base SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.26.1.160000.2.7
- kernel-syms SLES 16.0, Linux Micro Extras 6.2, SLES for SAP applications 16.0 6.12.0-160000.26.1
- kernel-azure SLES for SAP applications 16.0, SLES 16.0 6.12.0-160000.26.1
- kernel-obs-qa SLES for SAP applications 16.0, SLES 16.0 6.12.0-160000.26.1
suse advisories SUSE-SU-2026:20555-1SUSE-SU-2026:20599-1SUSE-SU-2026:20615-1SUSE-SU-2026:20570-1SUSE-SU-2025:03634-1SUSE-SU-2025:03633-1
- kernel-rt openSUSE Leap 16.0 6.12.0-160000.26.1
- dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.26.1
- kernel-64kb openSUSE Leap 16.0 6.12.0-160000.26.1
- kernel-syms openSUSE Leap 16.0 6.12.0-160000.26.1
- kernel-azure openSUSE Leap 16.0 6.12.0-160000.26.1
- kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.26.1
- kernel-source openSUSE Leap 16.0 6.12.0-160000.26.1
- kernel-default openSUSE Leap 16.0 6.12.0-160000.26.1
opensuse advisories openSUSE-SU-2026:20287-1
- git.kernel.org/stable/c/ceb645ac6ce052609ee5c8f819a80e8881789b04 commit
- git.kernel.org/stable/c/cdcb0ffd6448f6be898956913a42bd08e59fb2ae commit
- git.kernel.org/stable/c/1bb85b5c2bd43b687c3d54eb6328917f90dd38fc commit
- git.kernel.org/stable/c/5367cdeb75cb6c687ca468450bceb2602ab239d8 commit
- git.kernel.org/stable/c/ec7f98ff05f0649af0adeb4808c7ba23d6111ef9 commit
- git.kernel.org/stable/c/eaa420339658615d26c1cc95cd6cf720b9aebfca commit
- git.kernel.org/stable/c/cefc1caee9dd06c69e2d807edc5949b329f52b22 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-38535 updated cvss 2.3
kernel: phy: tegra: xusb: Fix unbalanced regulator disable in UTMI PHY mode
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 d ago
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/ceb645ac6ce052609ee5c8f819a80e8881789b04
patch
-
git.kernel.org
/stable/c/cdcb0ffd6448f6be898956913a42bd08e59fb2ae
patch
-
git.kernel.org
/stable/c/1bb85b5c2bd43b687c3d54eb6328917f90dd38fc
patch
-
git.kernel.org
/stable/c/5367cdeb75cb6c687ca468450bceb2602ab239d8
patch
-
git.kernel.org
/stable/c/ec7f98ff05f0649af0adeb4808c7ba23d6111ef9
patch
-
git.kernel.org
/stable/c/eaa420339658615d26c1cc95cd6cf720b9aebfca
patch
-
git.kernel.org
/stable/c/cefc1caee9dd06c69e2d807edc5949b329f52b22
patch
-
lists.debian.org
/debian-lts-announce/2025/10/msg00008.html
mailing-list, third-party-advisory
-
lists.debian.org
/debian-lts-announce/2025/10/msg00007.html
mailing-list, third-party-advisory
Sources
- CVE List CVE-2025-38535
- NVD CVE-2025-38535
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.