{"api_version":"1","generated_at":"2026-10-01T17:25:59+00:00","cve":"CVE-2026-93276","urls":{"html":"https://cve.report/CVE-2026-93276","api":"https://cve.report/api/cve/CVE-2026-93276.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-93276","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-93276"},"summary":{"title":"phy: renesas: phy-rcar-gen3-usb2: Fix devm action registration for disabled VBUS regulator","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nphy: renesas: phy-rcar-gen3-usb2: Fix devm action registration for disabled VBUS regulator\n\ndevm_regulator_get_exclusive() initialises the regulator with\nenable_count = 1, requiring the consumer to disable it before release.\n\nThe devm disable action was previously only registered when the caller\nexplicitly requested enable, so when the regulator was left in its initial\nenabled state without an explicit enable call, the cleanup path skipped\ndecrementing enable_count, triggering a WARN_ON during regulator\nrelease on device removal.\n\nFix this by always registering the devm disable action based on the actual\nenabled state via regulator_is_enabled(), regardless of whether the\ncaller requested an explicit enable. This covers both the explicitly\nenabled case and the initial state set by devm_regulator_get_exclusive().","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-24 16:17:24","updated_at":"2026-09-24 16:17:24"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/49c9b71b45081e5e5eeb507a2d6edb80d332dc59","name":"https://git.kernel.org/stable/c/49c9b71b45081e5e5eeb507a2d6edb80d332dc59","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/bf7fefbc26e292c08cfe7b6496b879109ef1475a","name":"https://git.kernel.org/stable/c/bf7fefbc26e292c08cfe7b6496b879109ef1475a","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/935f6e837a83b86b073a7601f699dc2c00e01322","name":"https://git.kernel.org/stable/c/935f6e837a83b86b073a7601f699dc2c00e01322","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-93276","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93276","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 24843404efe47eab1ee88d7475a0be0f2f6fd9db bf7fefbc26e292c08cfe7b6496b879109ef1475a git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 24843404efe47eab1ee88d7475a0be0f2f6fd9db 935f6e837a83b86b073a7601f699dc2c00e01322 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 24843404efe47eab1ee88d7475a0be0f2f6fd9db 49c9b71b45081e5e5eeb507a2d6edb80d332dc59 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.11","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.11 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.52 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.6 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/phy/renesas/phy-rcar-gen3-usb2.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"bf7fefbc26e292c08cfe7b6496b879109ef1475a","status":"affected","version":"24843404efe47eab1ee88d7475a0be0f2f6fd9db","versionType":"git"},{"lessThan":"935f6e837a83b86b073a7601f699dc2c00e01322","status":"affected","version":"24843404efe47eab1ee88d7475a0be0f2f6fd9db","versionType":"git"},{"lessThan":"49c9b71b45081e5e5eeb507a2d6edb80d332dc59","status":"affected","version":"24843404efe47eab1ee88d7475a0be0f2f6fd9db","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/phy/renesas/phy-rcar-gen3-usb2.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.11"},{"lessThan":"6.11","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.52","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.6","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.52","versionStartIncluding":"6.11","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.6","versionStartIncluding":"6.11","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"6.11","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nphy: renesas: phy-rcar-gen3-usb2: Fix devm action registration for disabled VBUS regulator\n\ndevm_regulator_get_exclusive() initialises the regulator with\nenable_count = 1, requiring the consumer to disable it before release.\n\nThe devm disable action was previously only registered when the caller\nexplicitly requested enable, so when the regulator was left in its initial\nenabled state without an explicit enable call, the cleanup path skipped\ndecrementing enable_count, triggering a WARN_ON during regulator\nrelease on device removal.\n\nFix this by always registering the devm disable action based on the actual\nenabled state via regulator_is_enabled(), regardless of whether the\ncaller requested an explicit enable. This covers both the explicitly\nenabled case and the initial state set by devm_regulator_get_exclusive()."}],"providerMetadata":{"dateUpdated":"2026-09-24T15:52:18.567Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/bf7fefbc26e292c08cfe7b6496b879109ef1475a"},{"url":"https://git.kernel.org/stable/c/935f6e837a83b86b073a7601f699dc2c00e01322"},{"url":"https://git.kernel.org/stable/c/49c9b71b45081e5e5eeb507a2d6edb80d332dc59"}],"title":"phy: renesas: phy-rcar-gen3-usb2: Fix devm action registration for disabled VBUS regulator","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-93276","datePublished":"2026-09-24T15:52:18.567Z","dateReserved":"2026-09-17T16:02:15.098Z","dateUpdated":"2026-09-24T15:52:18.567Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-24 16:17:24","lastModifiedDate":"2026-09-24 16:17:24","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"93276","Ordinal":"1","Title":"phy: renesas: phy-rcar-gen3-usb2: Fix devm action registration f","CVE":"CVE-2026-93276","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"93276","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nphy: renesas: phy-rcar-gen3-usb2: Fix devm action registration for disabled VBUS regulator\n\ndevm_regulator_get_exclusive() initialises the regulator with\nenable_count = 1, requiring the consumer to disable it before release.\n\nThe devm disable action was previously only registered when the caller\nexplicitly requested enable, so when the regulator was left in its initial\nenabled state without an explicit enable call, the cleanup path skipped\ndecrementing enable_count, triggering a WARN_ON during regulator\nrelease on device removal.\n\nFix this by always registering the devm disable action based on the actual\nenabled state via regulator_is_enabled(), regardless of whether the\ncaller requested an explicit enable. This covers both the explicitly\nenabled case and the initial state set by devm_regulator_get_exclusive().","Type":"Description","Title":"phy: renesas: phy-rcar-gen3-usb2: Fix devm action registration f"}]}}}