Vulnerability 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().
References
- https://git.kernel.org/stable/c/49c9b71b45081e5e5eeb507a2d6edb80d332dc59
- https://git.kernel.org/stable/c/935f6e837a83b86b073a7601f699dc2c00e01322
- https://git.kernel.org/stable/c/bf7fefbc26e292c08cfe7b6496b879109ef1475a
FAQ
What is CVE-2026-93276?
CVE-2026-93276 is a documented vulnerability. 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() initiali...
How severe is CVE-2026-93276?
CVSS scoring is not yet available for CVE-2026-93276. Check NVD for updates.
Is there a patch for CVE-2026-93276?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.