x86/mce: Set up the polling timer before CMCI discovery (CVE-2026-80727) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-80727

x86/mce: Set up the polling timer before CMCI discovery

Answer in brief

CVE-2026-80727 records a Unknown severity vulnerability in x86/mce: Set up the polling timer before CMCI discovery. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 3, 2026Updated Sep 3, 2026Source checked Sep 3, 2026First seen by HOL Sep 3, 2026Material review Sep 3, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=1f68ce2a027250aeeb1756391110cdc4dc97c797 <17ab68d0cf6a41bff61b1e13c6141d9e463736ae \|\| >=1f68ce2a027250aeeb1756391110cdc4dc97c797 <e708fc1566ebd4a2d3f2546e6310d64d362db80d \|\| >=1f68ce2a027250aeeb1756391110cdc4dc97c797 <4f4cba3947d2f0eceb32727e198ca2c149a653a9 \|\| >=1f68ce2a027250aeeb1756391110cdc4dc97c797 <a213dfaa2596c1c0dc4dae91c14fbfa499c03223	17ab68d0cf6a41bff61b1e13c6141d9e463736ae, e708fc1566ebd4a2d3f2546e6310d64d362db80d, 4f4cba3947d2f0eceb32727e198ca2c149a653a9, a213dfaa2596c1c0dc4dae91c14fbfa499c03223
Linux/Linuxgeneric	6.8	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 17ab68d0cf6a41bff61b1e13c6141d9e463736ae if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 3, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 3, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 3, 2026

Sources and claim methodology

Upstream source 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. ]

Quoted source text, attributed separately from HOL analysis.