CVE-2025-38535None▾ SunlitIn 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 shoul…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Nov 5.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
0.2% → 0.2%
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.
Linux >= 49d46e3c7e597e8b00c6fc16e6fd7a92044f4371 < ceb645ac6ce052609ee5c8f819a80e8881789b04Linux >= 49d46e3c7e597e8b00c6fc16e6fd7a92044f4371 < cdcb0ffd6448f6be898956913a42bd08e59fb2aeLinux >= 49d46e3c7e597e8b00c6fc16e6fd7a92044f4371 < 1bb85b5c2bd43b687c3d54eb6328917f90dd38fcLinux >= 49d46e3c7e597e8b00c6fc16e6fd7a92044f4371 < 5367cdeb75cb6c687ca468450bceb2602ab239d8Linux >= 49d46e3c7e597e8b00c6fc16e6fd7a92044f4371 < ec7f98ff05f0649af0adeb4808c7ba23d6111ef9Linux >= 49d46e3c7e597e8b00c6fc16e6fd7a92044f4371 < eaa420339658615d26c1cc95cd6cf720b9aebfcaLinux >= 49d46e3c7e597e8b00c6fc16e6fd7a92044f4371 < cefc1caee9dd06c69e2d807edc5949b329f52b22Linux 5.7Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99284Nonenet: skbuff: propagate shared-frag marker in skb_zerocopy()
CVE-2026-99283Nonenetfilter: conntrack: tcp: use UNACK timeout for non-closing RST packets
CVE-2026-99272Nonesmb: client: validate the data area in SMB2_read()
CVE-2026-99271NoneALSA: line6: Clear prev_fbuf on capture buffer release
CVE-2026-99273Noneksmbd: reserve space for the UTF-16 terminator in stream info
CVE-2026-99275Nonesmb: client: reject short SESSION_SETUP responses