CVE-2026-80727x86/mce: Set up the polling timer before CMCI discovery
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: x86/mce: Set up the polling timer before CMCI discovery I hit the following on one of my machines: mce: CPU0 BANK15 CMCI inherited storm ------------[ cut here ]------------ ODEBUG: assert_init not available (active state 0) object: (____ptrval____) object type: timer_list hint: 0x0 WARNING: lib/debugobjects.c:632 at debug_object_assert_init+0x178/0x230, CPU#0: swapper/0/0 CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 7.2.0-rc5 #3 PREEMPTLAZY RIP: 0010:debug_object_assert_init+0x18f/0x230 Call Trace: <TASK> __mod_timer mce_timer_kick cmci_discover intel_init_cmci mce_intel_feature_init mcheck_cpu_init identify_cpu identify_boot_cpu arch_cpu_finalize_init start_kernel A second splat follows right after, from timer_setup() finding that same timer already queued: ODEBUG: init active (active state 0) object: (____ptrval____) object type: timer_list hint: stub_timer+0x0/0x10 This is happening because CMCI storm detection is trying to modify the timer before latter was properly set up. Set up the timer first. __mcheck_cpu_setup_timer() only calls timer_setup(), and depends on neither the generic nor the vendor init. [ bp: Massage commit message. ]
Timeline
ID reserved
By Linux
- 8 days later
· 8 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (13 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 1f68ce2a027250aeeb1756391110cdc4dc97c797 – < 17ab68d0cf6a41bff61b1e13c6141d9e463736ae
- affected 1f68ce2a027250aeeb1756391110cdc4dc97c797 – < e708fc1566ebd4a2d3f2546e6310d64d362db80d
- affected 1f68ce2a027250aeeb1756391110cdc4dc97c797 – < 4f4cba3947d2f0eceb32727e198ca2c149a653a9
- affected 1f68ce2a027250aeeb1756391110cdc4dc97c797 – < a213dfaa2596c1c0dc4dae91c14fbfa499c03223
- affected 6.8
- unaffected < 6.8
- unaffected 6.12.105 – ≤ 6.12.*
- unaffected 6.18.45 – ≤ 6.18.*
- unaffected 7.1.9 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References4
- https://git.kernel.org/stable/c/17ab68d0cf6a41bff61b1e13c6141d9e463736ae (opens in a new tab)
- https://git.kernel.org/stable/c/e708fc1566ebd4a2d3f2546e6310d64d362db80d (opens in a new tab)
- https://git.kernel.org/stable/c/4f4cba3947d2f0eceb32727e198ca2c149a653a9 (opens in a new tab)
- https://git.kernel.org/stable/c/a213dfaa2596c1c0dc4dae91c14fbfa499c03223 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-70331 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-80727)Record last updated .