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

> A flaw in the Renesas USB2 PHY driver causes a kernel warning and potential instability during device removal due to incorrect regulator cleanup logic.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-93276, DEBIAN-CVE-2026-93276, GHSA-gfvh-9676-44ch, UBUNTU-CVE-2026-93276

## What is CVE-2026-93276?

CVE-2026-93276 is a denial of service vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

## Which versions are affected by CVE-2026-93276?


## How do I fix CVE-2026-93276?

Apply the vendor's patch.

## Is CVE-2026-93276 being exploited?

There is no known exploitation of CVE-2026-93276 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93276 and fix it if it is affected.

What it is: CVE-2026-93276 is a denial of service vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93276 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93276/ (Markdown: https://insights.sbomify.com/CVE-2026-93276/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93276
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93276
- OSV: https://osv.dev/vulnerability/CVE-2026-93276

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93276/
Summaries are generated and may contain mistakes; the official description above is the record.