Answer in brief
CVE-2026-93276 records a Unknown severity vulnerability in phy: renesas: phy-rcar-gen3-usb2: Fix devm action registration for disabled VBUS regulator. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=24843404efe47eab1ee88d7475a0be0f2f6fd9db <bf7fefbc26e292c08cfe7b6496b879109ef1475a || >=24843404efe47eab1ee88d7475a0be0f2f6fd9db <935f6e837a83b86b073a7601f699dc2c00e01322 || >=24843404efe47eab1ee88d7475a0be0f2f6fd9db <49c9b71b45081e5e5eeb507a2d6edb80d332dc59 | bf7fefbc26e292c08cfe7b6496b879109ef1475a, 935f6e837a83b86b073a7601f699dc2c00e01322, 49c9b71b45081e5e5eeb507a2d6edb80d332dc59 |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
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().
Quoted source text, attributed separately from HOL analysis.