{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93276 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-93276 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-93276 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-93276/ (Markdown: https://insights.sbomify.com/CVE-2026-93276/index.md)","id":"CVE-2026-93276","markdown":"https://insights.sbomify.com/CVE-2026-93276/index.md","name":"CVE-2026-93276","record":{"aliases":["BELL-CVE-2026-93276","DEBIAN-CVE-2026-93276","GHSA-gfvh-9676-44ch","UBUNTU-CVE-2026-93276"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel USB driver","requires_auth":"none","summary":"A flaw in the Renesas USB2 PHY driver causes a kernel warning and potential instability during device removal due to incorrect regulator cleanup logic.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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().","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"phy: renesas: phy-rcar-gen3-usb2: Fix devm action registration for disabled VBUS regulator","id":"CVE-2026-93276","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"RDMA/bnxt_re: Validate udata before executing commands","id":"CVE-2026-93277"},"packages":[],"prev":{"headline":"perf/x86/intel/pt: Fix stop/start with no update","id":"CVE-2026-93275"},"products":["Linux"],"published":"2026-09-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A flaw in the Renesas USB2 PHY driver causes a kernel warning and potential instability during device removal due to incorrect regulator cleanup logic.","url":"https://insights.sbomify.com/CVE-2026-93276/"}