CVE-2026-93276
Last modified
CVE-2026-93276 is a vulnerability of currently unknown severity. 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()..
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().
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 24843404efe47eab1ee88d7475a0be0f2f6fd9db, < bf7fefbc26e292c08cfe7b6496b879109ef1475a; >= 24843404efe47eab1ee88d7475a0be0f2f6fd9db, < 935f6e837a83b86b073a7601f699dc2c00e01322; >= 24843404efe47eab1ee88d7475a0be0f2f6fd9db, < 49c9b71b45081e5e5eeb507a2d6edb80d332dc59 |
| Linux | Linux | 6.11 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-93276?
How severe is CVE-2026-93276?
How do I fix CVE-2026-93276?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-93270In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93271In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93272In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93273In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93274In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93275In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93277In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93278In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93279In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93280In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93281In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93282In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-93276?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
