🛡️ CVE-2025-38010 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

phy: tegra: xusb: Use a bitmask for UTMI pad power state tracking

In the Linux kernel, the following vulnerability has been resolved:

phy: tegra: xusb: Use a bitmask for UTMI pad power state tracking

The current implementation uses bias_pad_enable as a reference count to

manage the shared bias pad for all UTMI PHYs. However, during system

suspension with connected USB devices, multiple power-down requests for

the UTMI pad result in a mismatch in the reference count, which in turn

produces warnings such as:

[ 237.762967] WARNING: CPU: 10 PID: 1618 at tegra186_utmi_pad_power_down+0x160/0x170

[ 237.763103] Call trace:

[ 237.763104] tegra186_utmi_pad_power_down+0x160/0x170

[ 237.763107] tegra186_utmi_phy_power_off+0x10/0x30

[ 237.763110] phy_power_off+0x48/0x100

[ 237.763113] tegra_xusb_enter_elpg+0x204/0x500

[ 237.763119] tegra_xusb_suspend+0x48/0x140

[ 237.763122] platform_pm_suspend+0x2c/0xb0

[ 237.763125] dpm_run_callback.isra.0+0x20/0xa0

[ 237.763127] __device_suspend+0x118/0x330

[ 237.763129] dpm_suspend+0x10c/0x1f0

[ 237.763130] dpm_suspend_start+0x88/0xb0

[ 237.763132] suspend_devices_and_enter+0x120/0x500

[ 237.763135] pm_suspend+0x1ec/0x270

The root cause was traced back to the dynamic power-down changes

introduced in commit a30951d31b25 ("xhci: tegra: USB2 pad power controls"),

where the UTMI pad was being powered down without verifying its current

state. This unbalanced behavior led to discrepancies in the reference

count.

To rectify this issue, this patch replaces the single reference counter

with a bitmask, renamed to utmi_pad_enabled. Each bit in the mask

corresponds to one of the four USB2 PHYs, allowing us to track each pad's

enablement status individually.

With this change:

  • The bias pad is powered on only when the mask is clear.
  • Each UTMI pad is powered on or down based on its corresponding bit

in the mask, preventing redundant operations.

  • The overall power state of the shared bias pad is maintained

correctly during suspend/resume cycles.

The mutex used to prevent race conditions during UTMI pad enable/disable

operations has been moved from the tegra186_utmi_bias_pad_power_on/off

functions to the parent functions tegra186_utmi_pad_power_on/down. This

change ensures that there are no race conditions when updating the bitmask.

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

Affected software

CVE-2025-38010 is recorded against 2 packages.

  • kernel (from 6.13.0 up to 6.14.8)
  • linux-kernel

Timeline and source

Published on 18 June 2025 and last revised on 15 July 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

CVE-2025-38010 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2025-06-18
Updated 2026-08-12
Modified 2026-07-15

Affected Packages

Software From version Fixed in
kernel 6.13.0 6.14.8
linux-kernel

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2025-38010 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.