{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72314 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72314 is a high-severity vulnerability in Linux, published on 15 Aug 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-72314 and fix it if it is affected.\n\nWhat it is: CVE-2026-72314 is a high-severity vulnerability in Linux, published on 15 Aug 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-72314 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-72314/ (Markdown: https://insights.sbomify.com/CVE-2026-72314/index.md)","id":"CVE-2026-72314","markdown":"https://insights.sbomify.com/CVE-2026-72314/index.md","name":"CVE-2026-72314","record":{"aliases":["BELL-CVE-2026-72314","DEBIAN-CVE-2026-72314","GHSA-g74q-qxv8-58hq","UBUNTU-CVE-2026-72314"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel regulator","requires_auth":"low_privilege","summary":"Incorrect deadlock detection in Linux kernel regulator code causes lock inconsistency on MIPS, potentially leading to system instability or denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nregulator: core: regulator_lock_two() should test for EDEADLK not EDEADLOCK\n\nCompare against -EDEADLK, which is what ww_mutex_lock() actually\nreturns and what every other deadlock check in this file already uses.\n\nFunction regulator_lock_two() acquires two regulators via\nregulator_lock_nested() -\u003e ww_mutex_lock().  On contention,\nww_mutex_lock() returns -EDEADLK, which is the caller's signal to drop\nthe lock it holds and retry the acquisition in the canonical order.\n\nHowever, regulator_lock_two() tests the return value against -EDEADLOCK\nrather than -EDEADLK.  On most architectures, EDEADLK and EDEADLOCK are\nthe same value, so the comparison happens to be correct and the bug is\ninvisible.  But on MIPS, SPARC, and PowerPC, those two errors have\ndifferent values.  The test is wrong: a genuine -EDEADLK backoff no\nlonger matches -EDEADLOCK, so instead of unlocking and retrying, the\ncode falls into WARN_ON(ret) and returns with only one of the two\nregulators locked.\n\nIn practice, this is a bug only on MIPS, because the regulator core is\nnot built or used on the other two platforms.\n\nIn general, EDEADLK is preferred over EDEADLOCK for new code.","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":"regulator: core: regulator_lock_two() should test for EDEADLK not EDEADLOCK","id":"CVE-2026-72314","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"smb: client: fix busy dentry warning on unmount after DIO","id":"CVE-2026-72315"},"packages":[],"prev":{"headline":"drm/fb-helper: Only consider active CRTCs for vblank sync","id":"CVE-2026-72313"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Linux"]},"summary":"Incorrect deadlock detection in Linux kernel regulator code causes lock inconsistency on MIPS, potentially leading to system instability or denial of service.","url":"https://insights.sbomify.com/CVE-2026-72314/"}