CVE-2026-93276

Kernel warning via skipped regulator cleanup

Published Sep 24, 2026 · Updated Sep 24, 2026

Improper cleanup in the Renesas USB2 PHY driver in Linux 6.11 allows attackers to trigger a kernel WARN_ON during device removal. The rcar_gen3_phy_usb2_vbus_regulator_get_exclusive_enable function registers the managed disable action only after an explicit enable, so cleanup can leave the regulator enable count elevated. Device removal on an affected Renesas SoC is required; service interruption occurs only when panic_on_warn converts the warning into a kernel panic.

CVSS severityUnavailable
Unscored
EPSS probability0.18%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Improper cleanup in the Renesas USB2 PHY driver in Linux 6.11 allows attackers to trigger a kernel WARN_ON during device removal. The rcar_gen3_phy_usb2_vbus_regulator_get_exclusive_enable function registers the managed disable action only after an explicit enable, so cleanup can leave the regulator enable count elevated. Device removal on an affected Renesas SoC is required; service interruption occurs only when panic_on_warn converts the warning into a kernel panic.

The record

CVE
CVE-2026-93276
Published
Sep 24, 2026
Updated
Sep 24, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Sep 24, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 24, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=24843404efe47eab1ee88d7475a0be0f2f6fd9db <49c9b71b45081e5e5eeb507a2d6edb80d332dc59
  2. Affected versionversion=24843404efe47eab1ee88d7475a0be0f2f6fd9db <935f6e837a83b86b073a7601f699dc2c00e01322
  3. Affected versionversion=24843404efe47eab1ee88d7475a0be0f2f6fd9db <bf7fefbc26e292c08cfe7b6496b879109ef1475a
  4. Affected versionversion=6.11

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=24843404efe47eab1ee88d7475a0be0f2f6fd9db <49c9b71b45081e5e5eeb507a2d6edb80d332dc59; version=24843404efe47eab1ee88d7475a0be0f2f6fd9db <935f6e837a83b86b073a7601f699dc2c00e01322; version=24843404efe47eab1ee88d7475a0be0f2f6fd9db <bf7fefbc26e292c08cfe7b6496b879109ef1475a; version=6.11

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started