{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80727 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80727 is a vulnerability in Linux, published on 3 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-80727 and fix it if it is affected.\n\nWhat it is: CVE-2026-80727 is a vulnerability in Linux, published on 3 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-80727 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-80727/ (Markdown: https://insights.sbomify.com/CVE-2026-80727/index.md)","id":"CVE-2026-80727","markdown":"https://insights.sbomify.com/CVE-2026-80727/index.md","name":"CVE-2026-80727","record":{"aliases":["BELL-CVE-2026-80727","DEBIAN-CVE-2026-80727","GHSA-5fmr-wwgg-gfqm","UBUNTU-CVE-2026-80727"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A race condition in the Linux kernel x86 MCE subsystem causes a kernel warning and potential instability during CPU initialization.","user_interaction":"not_required","vuln_class":"race_condition"},"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\nx86/mce: Set up the polling timer before CMCI discovery\n\nI hit the following on one of my machines:\n\n  mce: CPU0 BANK15 CMCI inherited storm\n  ------------[ cut here ]------------\n  ODEBUG: assert_init not available (active state 0) object: (____ptrval____) object type: timer_list hint: 0x0\n  WARNING: lib/debugobjects.c:632 at debug_object_assert_init+0x178/0x230, CPU#0: swapper/0/0\n  CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 7.2.0-rc5 #3 PREEMPTLAZY\n  RIP: 0010:debug_object_assert_init+0x18f/0x230\n  Call Trace:\n   \u003cTASK\u003e\n   __mod_timer\n   mce_timer_kick\n   cmci_discover\n   intel_init_cmci\n   mce_intel_feature_init\n   mcheck_cpu_init\n   identify_cpu\n   identify_boot_cpu\n   arch_cpu_finalize_init\n   start_kernel\n\nA second splat follows right after, from timer_setup() finding that same\ntimer already queued:\n\n  ODEBUG: init active (active state 0) object: (____ptrval____) object type: timer_list hint: stub_timer+0x0/0x10\n\nThis is happening because CMCI storm detection is trying to modify the timer\nbefore latter was properly set up.\n\nSet up the timer first. __mcheck_cpu_setup_timer() only calls timer_setup(),\nand depends on neither the generic nor the vendor init.\n\n  [ bp: Massage commit message. ]","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":"x86/mce: Set up the polling timer before CMCI discovery","id":"CVE-2026-80727","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Revert \"drm/amdgpu: fix aperture mapping leak\"","id":"CVE-2026-80728"},"packages":[],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2026-80726"},"products":["Linux"],"published":"2026-09-03","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-09-03","vendors":["Linux"]},"summary":"A race condition in the Linux kernel x86 MCE subsystem causes a kernel warning and potential instability during CPU initialization.","url":"https://insights.sbomify.com/CVE-2026-80727/"}