CVE-2026-80727: x86/mce: Set up the polling timer before CMCI discovery

Published Sep 3, 2026
·
Updated

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: assertinit not available (active state 0) object: (ptrval) object type: timerlist hint: 0x0 WARNING: lib/debugobjects.c:632 at debugobjectassertinit+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:debugobjectassertinit+0x18f/0x230 Call Trace: <TASK> modtimer mcetimerkick cmcidiscover intelinitcmci mceintelfeatureinit mcheckcpuinit identifycpu identifybootcpu archcpufinalizeinit startkernel

A second splat follows right after, from timersetup() finding that same timer already queued:

ODEBUG: init active (active state 0) object: (ptrval) object type: timerlist hint: stubtimer+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. mcheckcpusetuptimer() only calls timersetup(), and depends on neither the generic nor the vendor init.

[ bp: Massage commit message. ]

Affected Software

1 affected component
Linux Linux kernel

Event History

Sep 3, 2026
CVE Published
via MITRE·08:21 AM
Data Sourced
via MITRE·08:21 AM
Description

Frequently Asked Questions

1

What conditions trigger this issue?

The issue is triggered when CMCI storm detection attempts to modify the machine-check polling timer before that timer has been initialized. The reported path involves CMCI discovery during CPU machine-check initialization.

2

What symptoms indicate that a system may be affected?

Affected systems may log an "mce: CPU0 BANK15 CMCI inherited storm" message followed by debugobjects warnings. The warnings include "assert_init not available" from debug_object_assert_init and may be followed by a timer_setup() warning that the same timer is already queued.

3

What is the available remediation?

Apply a Linux kernel update containing the fix that initializes the polling timer before CMCI discovery. The provided stable kernel references identify commits carrying the correction.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203