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

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

[AL-KERNEL]

CVE: CVE-2026-80727
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: x86/mce: Set up the polling timer before CMCI discovery [ Upstream
Commit: 17ab68d0cf6a41bff61b1e13c6141d9e463736ae
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=17ab68d0cf6a41bff61b1e13c6141d9e463736ae
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80727
Analysis date: Thu, 03 Sep 2026 04:55:20 -0400
ActionableScore: 2
ActionableScore lower bound: 1
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
No one-sentence report phrase was found.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-80727 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80727

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: LOW
Manual review required: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-80727	LOW	https://www.kernelcve.org/list/?q=CVE-2026-80727 CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H';CWE-665;CWE-703;CWE-754;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.2';DESCR 'An initialization order bug in x86/mce can let CMCI storm handling call mce_timer_kick before the polling timer has been set up. This can modify an uninitialized timer_list during early CPU machine check initialization and produce debugobjects warnings or a boot time kernel failure on affected systems. For the CVSS the PR:H is used in the paranoid local interpretation because a reliable software trigger would normally require administrative control over low level machine check or hardware error conditions, while the realistic trigger is hardware specific and not a normal user interface. The issue is not network reachable and is not triggered by packet traffic or remote input. Impact is denial of service through warning, panic, or boot failure only. No confidentiality or integrity impact is assigned because the patch shows an initialization ordering fault rather than UAF, OOB access, arbitrary write, or information disclosure.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 2)	YES	DANGER TIMER HARDWARE LINUS  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	YES	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=2
ActionableScoreLower=1

1. ActionableScore
* Conservative score: 1
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate / Low-like**::

2. Signal breakdown
* Firmware-mediated or hardware-mediated external influence: +1. The trigger depends on CMCI storm behavior during early x86 MCE initialization, not on normal user input.
* Reliable kernel crash / strong DoS: +1 in paranoid scoring only. The patch shows debugobjects warnings and possible boot-time failure, but the provided evidence is mainly warning/splat behavior rather than a demonstrated reliable panic on ordinary systems.
* Physical-only or rare hardware-only condition: -2. The issue depends on specific Intel CMCI or machine-check state during boot and is not a generally reachable software interface.
* No memory corruption score. The patch only reorders timer initialization before CMCI discovery and does not show UAF, double-free, OOB write, type confusion, arbitrary write, or attacker-controlled reclaim.
* No C/I impact. There is no supported confidentiality or integrity primitive.

3. Reachability analysis
The bug is reached during early CPU machine-check initialization, specifically when CMCI storm detection calls mce_timer_kick before timer_setup has initialized the polling timer. A local unprivileged user cannot normally trigger this path. Containers and namespaces do not meaningfully reduce the privilege requirement because the path is boot-time CPU hardware initialization, not a namespaced syscall or device API. The affected subsystem is common on x86, but the triggering condition is hardware-state specific and not network reachable.

4. Severity interpretation
This behaves like a hardware-specific initialization-order DoS or warning condition, not an Important-class vulnerability. Theoretical impact is limited to warning, panic-on-warn environments, or boot-time failure on affected hardware. Realistic exploitation evidence is weak because there is no software-accessible attacker primitive and no memory lifetime or overwrite issue.

5. One-sentence report phrase
An x86 MCE initialization order bug can let CMCI storm handling modify the polling timer before timer_setup, causing debugobjects warnings or possible boot-time DoS on affected hardware, with no network reachability, no practical unprivileged trigger, and no evidence of confidentiality, integrity, or privilege-escalation impact.

6. Manual review recommendation
NO MANUAL CHECK NEEDED. This is a low-actionability hardware-specific initialization ordering issue with no demonstrated memory corruption, no network trigger, and no plausible LPE path from the provided patch context.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: x86/mce: Set up the polling timer before CMCI discovery [ Upstream
Commit: 17ab68d0cf6a41bff61b1e13c6141d9e463736ae
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=17ab68d0cf6a41bff61b1e13c6141d9e463736ae

Changed files:
  lib/debugobjects.c
  arch/x86/kernel/cpu/mce/core.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=17ab68d0cf6a41bff61b1e13c6141d9e463736ae

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-80727 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80727

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.2

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 1
  Paranoid ActionableScore: 2

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).