VulnerabilityPublished 18 Jun 2025Updated 5 Nov 2026

CVE-2025-38010: Linux kernel · phy: tegra: xusb: Use a bitmask for UTMI pad power state tracking

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in ba25131b3c1ceec303839b2462586d7673788197 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:04 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

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 ba25131b3c1ceec303839b2462586d7673788197, b47158fb42959c417ff2662075c0d46fb783d5d1, 628bec9ed68a2204184fc8230a2609075b08666e +1

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Jun 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to ba25131b3c1ceec303839b2462586d7673788197, b47158fb42959c417ff2662075c0d46fb783d5d1, 628bec9ed68a2204184fc8230a2609075b08666e or 1db527f0cb8f677adadd4e28e5bc77aaf5d4e4c9.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ a30951d31b250bf3479c00e93646b6cc6fb42a56, < ba25131b3c1ceec303839b2462586d7673788197	Fixed in ba25131b3c1ceec303839b2462586d7673788197
LinuxLinux	Affected ≥ a30951d31b250bf3479c00e93646b6cc6fb42a56, < b47158fb42959c417ff2662075c0d46fb783d5d1	Fixed in b47158fb42959c417ff2662075c0d46fb783d5d1
LinuxLinux	Affected ≥ a30951d31b250bf3479c00e93646b6cc6fb42a56, < 628bec9ed68a2204184fc8230a2609075b08666e	Fixed in 628bec9ed68a2204184fc8230a2609075b08666e
LinuxLinux	Affected ≥ a30951d31b250bf3479c00e93646b6cc6fb42a56, < 1db527f0cb8f677adadd4e28e5bc77aaf5d4e4c9	Fixed in 1db527f0cb8f677adadd4e28e5bc77aaf5d4e4c9
LinuxLinux	Affected =6.3	Fixed in–

Description

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.

References

Community reviews

Loading reviews…