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

phy: renesas: phy-rcar-gen3-usb2: Fix devm action registration for disabled VBUS regulator

devm_regulator_get_exclusive() initialises the regulator with
enable_count = 1, requiring the consumer to disable it before release.

The devm disable action was previously only registered when the caller
explicitly requested enable, so when the regulator was left in its initial
enabled state without an explicit enable call, the cleanup path skipped
decrementing enable_count, triggering a WARN_ON during regulator
release on device removal.

Fix this by always registering the devm disable action based on the actual
enabled state via regulator_is_enabled(), regardless of whether the
caller requested an explicit enable. This covers both the explicitly
enabled case and the initial state set by devm_regulator_get_exclusive().
Published: 2026-09-24
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Kernel Stability Disruption
Action: Apply Patch
AI Analysis

Impact

The bug resides in the Renesas R-Car Gen3 USB2 driver within the Linux kernel. The driver calls devm_regulator_get_exclusive(), which initializes the regulator with an enable counter of one. The device manager is expected to register a cleanup routine that decrements this counter when the device is removed. However, the cleanup routine was only registered when the caller explicitly enabled the VBUS regulator. When the regulator remained in its initial enabled state without an explicit enable call, the cleanup path never decremented the counter, causing a WARN_ON during regulator release. The failure to decrement the counter leaves the regulator in an invalid state and can cause driver mis‑behavior and system instability.

Affected Systems

This issue is contained entirely in the Linux kernel’s core regulator framework as exercised by the Renesas R-Car Gen3 USB2 driver. Any Linux distribution that ships a kernel containing this driver or a derivative that relies on the same regulator logic is affected. No specific vendor version numbers are supplied, so the vulnerability exists in all builds prior to the commit that introduced the fix.

Risk and Exploitability

The EPSS score is < 1% and the vulnerability is not listed in the CISA KEV catalog. There are no publicly known exploits. The flaw requires local or privileged access to trigger a device removal of the affected hardware and does not provide code execution, privilege escalation, or data compromise. Consequently, the overall risk is low, but the instability caused by warnings or potential driver crashes could impact availability in critical environments.

Generated by OpenCVE AI on October 1, 2026 at 17:40 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a release that contains the recent patch for the Renesas R-Car Gen3 USB2 driver.
  • If a kernel upgrade cannot be applied immediately, blacklist or disable the affected driver so that the USB2 controller is no longer loaded.
  • Continuously monitor system logs for WARN_ON entries related to regulator cleanup and take corrective action if stalls or repeated failures are observed.

Generated by OpenCVE AI on October 1, 2026 at 17:40 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 29 Sep 2026 13:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-459
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate


Thu, 24 Sep 2026 16:00:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: phy: renesas: phy-rcar-gen3-usb2: Fix devm action registration for disabled VBUS regulator devm_regulator_get_exclusive() initialises the regulator with enable_count = 1, requiring the consumer to disable it before release. The devm disable action was previously only registered when the caller explicitly requested enable, so when the regulator was left in its initial enabled state without an explicit enable call, the cleanup path skipped decrementing enable_count, triggering a WARN_ON during regulator release on device removal. Fix this by always registering the devm disable action based on the actual enabled state via regulator_is_enabled(), regardless of whether the caller requested an explicit enable. This covers both the explicitly enabled case and the initial state set by devm_regulator_get_exclusive().
Title phy: renesas: phy-rcar-gen3-usb2: Fix devm action registration for disabled VBUS regulator
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-19T09:08:30.634Z

Reserved: 2026-09-17T16:02:15.098Z

Link: CVE-2026-93276

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-24T16:17:24.797

Modified: 2026-10-19T10:17:19.130

Link: CVE-2026-93276

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-09-24T00:00:00Z

Links: CVE-2026-93276 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-01T17:45:09Z

Weaknesses