{"id":"CVE-2026-93276","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nphy: renesas: phy-rcar-gen3-usb2: Fix devm action registration for disabled VBUS regulator\n\ndevm_regulator_get_exclusive() initialises the regulator with\nenable_count =…","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nphy: renesas: phy-rcar-gen3-usb2: Fix devm action registration for disabled VBUS regulator\n\ndevm_regulator_get_exclusive() initialises the regulator with\nenable_count =…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 24843404efe47eab1ee88d7475a0be0f2f6fd9db < bf7fefbc26e292c08cfe7b6496b879109ef1475a","Linux >= 24843404efe47eab1ee88d7475a0be0f2f6fd9db < 935f6e837a83b86b073a7601f699dc2c00e01322","Linux >= 24843404efe47eab1ee88d7475a0be0f2f6fd9db < 49c9b71b45081e5e5eeb507a2d6edb80d332dc59","Linux 6.11"],"published":"2026-09-24","updated":"2026-09-24","sourceUpdated":"2026-09-24T16:17:24.797","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-93276","references":[{"url":"https://git.kernel.org/stable/c/49c9b71b45081e5e5eeb507a2d6edb80d332dc59","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/935f6e837a83b86b073a7601f699dc2c00e01322","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/bf7fefbc26e292c08cfe7b6496b879109ef1475a","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"tags":["nvd","cve.org"],"ingestedAt":"2026-09-24T16:47:15.840Z","slug":"CVE-2026-93276","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nphy: renesas: phy-rcar-gen3-usb2: Fix devm action registration for disabled VBUS regulator\n\ndevm_regulator_get_exclusive() initialises the regulator with\nenable_count = 1, requiring the consumer to disable it before release.\n\nThe devm disable action was previously only registered when the caller\nexplicitly requested enable, so when the regulator was left in its initial\nenabled state without an explicit enable call, the cleanup path skipped\ndecrementing enable_count, triggering a WARN_ON during regulator\nrelease on device removal.\n\nFix this by always registering the devm disable action based on the actual\nenabled state via regulator_is_enabled(), regardless of whether the\ncaller requested an explicit enable. This covers both the explicitly\nenabled case and the initial state set by devm_regulator_get_exclusive().\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}