[CVE-2026-97423][MODERATE REGULAR] cxl/region: Validate partition index before array access [ Upstream

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-97423
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: cxl/region: Validate partition index before array access [ Upstream
Commit: 06322da06116f1ee52271dd4d84dc69580087df7
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=06322da06116f1ee52271dd4d84dc69580087df7
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97423
Analysis date: Thu, 24 Sep 2026 14:16:38 -0400
ActionableScore: 1
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
No one-sentence report phrase was found.

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

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

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 REGULAR
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-97423	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-97423 CHECK WITH IMPACT FROM ORIG NN IMPORTANT	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H';CWE-125;CWE-129;*CWE-20;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.2';DESCR 'An out of bounds read in the CXL region creation path occurs because construct_region uses cxled part as an index into cxlds part without first rejecting a negative unresolved partition value. If part remains at its initial value of minus one, the kernel reads memory before the part array and uses the resulting value as the region mode during region creation. This is a local CXL management path and is not directly network reachable. For the CVSS the PR:H reflects that creating or managing CXL regions normally requires administrative control over CXL devices and their sysfs management interfaces. The base impact is limited availability because the patch does not demonstrate an information disclosure primitive, a write primitive, or privilege escalation. For the paranoid score the out of bounds read can influence region configuration and may cause limited confidentiality or integrity impact together with a more serious availability failure. The issue requires specialized CXL hardware and a state where the partition index has not been resolved.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1)	YES	OOB SIMPLEFIX IMPROVEONLY  LOWERED_FROM_HIGH_BASED_ON_GUESSCVSS  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4	NO	NO	checked

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

ActionableScore=1
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=UNKNOWN
ImportantCandidate=NO
ManualReview=RECOMMENDED
AutoDowngradeAllowed=YES

1. ActionableScore

* Raw conservative score: 1
* Conservative score: 1
* Raw paranoid score: 1
* Paranoid score: 1
* No floor or cap applied.
* Final recommended bucket: **Ordinary Moderate**::

2. Signal breakdown

* +1 Weak indirect corruption candidate. A negative unresolved `cxled->part` value is used as an array index, causing a concrete out of bounds read from memory preceding `cxlds->part[]`. The value is then consumed as the region mode argument to `__create_region`.
* +0 Reliable kernel crash or strong DoS. The supplied patch does not demonstrate a crash, panic, invalid dereference beyond the bounded array under-read, or host-wide availability effect.
* +0 Confidentiality impact. There is no demonstrated path that copies the out of bounds value to userspace, network output, device-visible output, or another disclosure sink.
* +0 Integrity impact. The patch establishes a read-only invalid array access. It does not establish an attacker-controlled write, modification of protected data, or a security-sensitive state change.
* +0 Strong semantic reinterpretation. The out of bounds value is used as a mode, but the evidence does not establish attacker control over the read value or a materially security-relevant semantic transition.
* +0 Local unprivileged trigger. The supplied context does not show that an ordinary user can invoke the complete CXL region construction path.
* +0 Host-admin penalty. Host-admin-equivalent privilege is likely relevant for CXL region management, but the supplied patch does not show the relevant sysfs permissions, capability checks, or call sites. Therefore this remains UNKNOWN and no unsupported negative penalty is applied.
* +0 Hardware or niche subsystem penalty. CXL hardware may be a prerequisite, but the supplied evidence does not establish that it is rare or attacker-inaccessible in the evaluated environment.
* Controlled reclaim not demonstrated.
* Arbitrary write not demonstrated.
* Remote reachability not established.
* No UAF, stale reference, refcount mutation, double release, or lifetime violation is established.
* No repeated release or refcount operation exists.
* No extra Availability point is awarded because no concrete crash or distinct persistent unavailability mechanism is demonstrated.

3. Reachability analysis

The affected operation is `construct_region()` in the CXL region-management path. The vulnerable state requires `cxled->part` to remain unresolved at its initial value of minus one when a region construction attempt occurs.

The patch alone does not show the userspace entry point, sysfs attribute permissions, capability checks, or whether a less privileged delegated CXL-management actor can invoke the complete sequence. CXL region creation is generally a local device-management operation, but this general expectation is insufficient to set `HostAdminRequired=YES` under the requested evidence rules.

No network path is shown. No namespace-scoped capability path is shown. No evidence establishes that a container or user namespace can create or manipulate the required CXL decoder and region state. Special CXL hardware and an unresolved partition state are required, but neither the practical availability of that hardware nor the repeatability of the condition is established by the supplied context.

4. Primitive and severity interpretation

The exact primitive is a negative array index resulting in an out of bounds read of memory immediately before `cxlds->part[]`. The resulting memory value is used as a region mode argument. This is not a UAF, active-object lifetime violation, write primitive, controlled type confusion, or repeated refcount mutation.

The patch establishes invalid-state handling and prevents a read-only out of bounds access by returning `-EBUSY` when the partition index is unresolved. It does not establish that the read value is attacker-controlled, disclosed, used as a pointer, or converted into a kernel write. It also does not establish a crash, privilege escalation, policy bypass, or corruption of another principals data.

The issue is therefore `CLASS_C`: an invalid-state and bounded out of bounds read condition with no independently useful exploitation primitive demonstrated. The practical consequence may include failed or incorrect CXL region creation, but this remains below the threshold for an Important candidate on the available evidence.

`AutoDowngradeAllowed=YES` is appropriate because no unresolved UAF, write-like lifetime mutation, controlled corruption, ownership violation, or security-boundary bypass remains.

5. One-sentence report phrase

A negative unresolved CXL partition index could be used for an out of bounds read during region construction, potentially causing invalid region-mode handling, but no disclosure, write primitive, privilege escalation, or reliable crash is established.

6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Review the callers of `construct_region()`, validation in `__create_region()`, the layout immediately preceding `cxlds->part[]`, and the exact sysfs or ioctl permission model to determine whether the read value can produce a stronger operational consequence.

7. Call-site confidence

Call-site confidence: low

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

Patch: cxl/region: Validate partition index before array access [ Upstream
Commit: 06322da06116f1ee52271dd4d84dc69580087df7
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=06322da06116f1ee52271dd4d84dc69580087df7

Changed files:
  drivers/cxl/core/region.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=06322da06116f1ee52271dd4d84dc69580087df7

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

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

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:L
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H
  The Best / paranoid CVSS score: 5.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: unknown
  Paranoid ActionableScore: 1

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: NO
Published priority for this report (same as in Subject): MODERATE REGULAR

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