PT-2026-84925 · Git+1 · Kernel+1

CVE-2026-80727

·

Published

2026-09-03

·

Updated

2026-09-03

None

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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: 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. ]

Exploit

Found an issue in the description? Have something to add? Feel free to write us 👾

Related Identifiers

CVE-2026-80727

Affected Products

Kernel
Linux