phy: tegra: xusb: Fix unbalanced regulator disable in UTMI PHY mode
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 49d46e3c7e597e8b00c6fc16e6fd7a92044f4371 · < eaa420339658615d26c1cc95cd6cf720b9aebfca| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s Tegra XUSB UTMI PHY code can incorrectly attempt to disable an always-on regulator when transitioning from USB device mode to no role, causing an unbalanced-disable warning. The input does not describe an attacker action or specify network access, authentication, or user-interaction conditions.
Engineers running Linux kernels with the Tegra XUSB UTMI PHY should check their installations; affected versions are not specified.