[CVE-2026-89570][MODERATE 7.0] cxl/mce: Make the MCE notifier per-region [ Upstream

[CVE-2026-89570][MODERATE 7.0] cxl/mce: Make the MCE notifier per-region [ Upstream

[AL-KERNEL]

CVE: CVE-2026-89570
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: cxl/mce: Make the MCE notifier per-region [ Upstream
Commit: 5563db13c9528a56c7161260ec75ec8690dc5608
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5563db13c9528a56c7161260ec75ec8690dc5608
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-89570
Analysis date: Sat, 12 Sep 2026 04:17:56 -0400
ActionableScore: 5
ActionableScore lower bound: 4
Actionable bucket: Actionable Moderate / Strong Important candidate requiring manual review
Manual review required: YES

Summary:
No one-sentence report phrase was found.

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

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

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: MODERATE 7.0
Manual review required: YES

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

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

CVE-2026-89570	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-89570 CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H';*CWE-416;**CWE-476;*CWE-664;CWE-362;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7';DESCR 'A lifetime bug in the CXL MCE notifier can make the MCE handler use a notifier object tied to cxl_memdev_state after the relevant memory device or endpoint state is no longer valid. This can result in a NULL-pointer dereference or a use-after-free when a machine check is handled for a CXL region with an extended linear cache. For the CVSS the PR:L is used for the paranoid score because a reduced-capability root, service account, or delegated management context may be able to influence CXL region or device lifetime without full host control. The issue is not network reachable and requires local access plus a specific CXL hardware and region configuration. Impact is at least local denial of service via kernel crash and in worst case may allow confidentiality or integrity impact due to kernel use-after-free, so it should be reviewed manually.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate / Strong Important candidate requiring manual review (with actual score 5)  SKIP CVE-2026-89570 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: url YES  NO NO unknown 	MAYBE	OOB DANGER NULLPTR INIT UAF HARDWARE KPANIC 	-	-	checked

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

ActionableScore=5
ActionableScoreLower=4
PrimitiveClass=CLASS_B
RealUAF=YES
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=NO
ImportantCandidate=YES
ManualReview=REQUIRED
AutoDowngradeAllowed=NO

1. ActionableScore

* Raw conservative score: 3
* Conservative score: 4
* Applied conservative floor/cap: Real UAF floor 4 applied because a concrete post-lifetime notifier use is established and host-admin-equivalent triggering is not positively established.
* Raw paranoid score: 4
* Paranoid score: 5
* Applied paranoid floor/cap: Real UAF floor 5 applied because the stale object is consumed in active MCE handling and can drive nontrivial memory-error handling logic, not merely a shallow cleanup fault.
* Final recommended bucket: **Actionable Moderate / Strong Important candidate requiring manual review**::

2. Signal breakdown

Positive signals:

* +2 Real UAF / active lifetime violation: the MCE notifier was stored in `struct cxl_memdev_state`, but the MCE handler could run after the related memdev or endpoint state was no longer valid.
* +1 Reliable kernel crash / strong DoS: the commit explicitly says the lifetime issue can lead to NULL dereferences and use-after-free in the MCE handler.
* +1 paranoid weak structured-state concern: the stale handler path uses CXL device or region-derived state to compute an aliased SPA and may call `memory_failure()` / `set_mce_nospec()` on a derived PFN. This is more than a purely passive stale read, but not enough for CLASS_A.

Negative or non-awarded signals:

* Remote reachability not awarded: this is not network-triggerable.
* Local unprivileged trigger not awarded: no evidence shows an ordinary local user can create the complete CXL region lifetime plus MCE trigger sequence.
* Host-admin penalty not applied: CXL region/device management is likely privileged, but the supplied evidence does not positively prove the complete trigger requires host-admin-equivalent privilege.
* Namespace-scoped privilege not awarded: no namespace-scoped trigger chain is shown.
* Controlled reclaim not demonstrated.
* Arbitrary write not demonstrated.
* Confidentiality and integrity bonuses not awarded: no disclosure, arbitrary write, credential manipulation, or controlled replacement is established.
* Concrete repeated release/refcount signal not awarded: the patch does not show first put/free, surviving exact reference, then second lifetime mutation on the same reference.
* Structured stale-object exploitation leverage not fully awarded as strong leverage: the stale object is active and structured, but attacker-shaped replacement or controlled post-free contents are not shown.
* Extra availability not awarded: crash/DoS is already counted once.
* Strong LPE / CLASS_A not awarded: no controlled reclaim, callback hijack, refcount takeover, or demonstrated privilege escalation is established.

Repeated-release/refcount check:

* First release can end lifetime: not directly shown in the supplied diff.
* Exact same reference survives to a second release: not established.
* Second operation is a real lifetime/refcount mutation: not established.
* +1 Concrete repeated release/refcount awarded: no.
* Paranoid repeated-refcount leverage awarded: no.
* FLOOR 5 applied: yes, but due active structured UAF processing, not due repeated release/refcount.

3. Reachability analysis

The vulnerable path is the CXL MCE notifier handler. The bug requires a CXL region with an extended linear cache, because the new registration is limited to regions with `cache_size`. It also requires an MCE event that reaches the notifier while the old per-memdev lifetime model is invalid.

The likely practical trigger involves CXL device or region lifetime changes plus a machine-check event. CXL region setup and teardown are normally administrative operations, but the supplied evidence does not prove the complete attacker model, so `HostAdminRequired=UNKNOWN` rather than YES. No evidence shows that the complete operation is namespace-scoped, so `NamespaceScopedPrivilege=NO`.

There is no direct network path. There is a material hardware/configuration dependency: CXL hardware with extended linear cache and CONFIG support for CXL MCE handling. Race or timing repeatability is unresolved, because the relevant event is asynchronous MCE handling combined with object lifetime teardown.

4. Primitive and severity interpretation

The exact primitive is a lifetime mismatch for a notifier object. The old code derives `struct cxl_memdev_state` from the notifier block and then follows memdev/endpoint state. If that state has already gone away, the MCE handler can dereference invalid state or use freed memory.

This is an active structured-object UAF rather than fixed stale storage. It is not merely cleanup/destructor-only, because the stale reference is consumed during MCE handling and can affect alias calculation and memory-failure handling. However, the supplied evidence does not establish controlled reclaim, attacker-controlled replacement contents, arbitrary kernel read/write, callback control, or a demonstrated LPE chain.

Primitive class is CLASS_B. Demonstrated consequence is local host DoS through NULL dereference or UAF-triggered crash. Speculative consequence is stronger kernel memory corruption if stale CXL state is reused in a meaningful way, but that is not proven. ImportantCandidate is YES because the bug is a real active kernel UAF in asynchronous MCE handling and needs Important-vs-Moderate review. AutoDowngradeAllowed is NO because automatic closure would discard unresolved active lifetime-corruption leverage.

Likely operational severity is Actionable Moderate with manual review required, not a confirmed Strong Important issue from the supplied evidence alone.

5. One-sentence report phrase

A CXL MCE notifier lifetime mismatch can cause the MCE handler to use stale memdev or endpoint state, leading to NULL dereference or use-after-free during machine-check handling on systems with CXL extended linear cache.

6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: the patch directly establishes a real kernel UAF/lifetime bug in an asynchronous MCE handler, and the stale structured state is used in nontrivial CXL memory-error processing, but the available evidence does not prove or exclude stronger exploitation leverage.

7. Call-site confidence

Call-site confidence: medium

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

Patch: cxl/mce: Make the MCE notifier per-region [ Upstream
Commit: 5563db13c9528a56c7161260ec75ec8690dc5608
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5563db13c9528a56c7161260ec75ec8690dc5608

Changed files:
  drivers/cxl/core/mbox.c
  drivers/cxl/core/mce.c
  drivers/cxl/core/region.c
  drivers/cxl/cxl.h
  drivers/cxl/cxlmem.h

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=5563db13c9528a56c7161260ec75ec8690dc5608

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

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

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:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
  The Best / paranoid CVSS score: 7

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: 4
  Paranoid ActionableScore: 5

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: MODERATE
KPANIC detected for this report: YES
Published priority for this report (same as in Subject): MODERATE 7.0

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).