[CVE-2026-74274][LOW] cxl/region: Fill first free targets[] slot during auto-discovery [ Upstream

[CVE-2026-74274][LOW] cxl/region: Fill first free targets[] slot during auto-discovery [ Upstream

[AL-KERNEL]

CVE: CVE-2026-74274
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: cxl/region: Fill first free targets[] slot during auto-discovery [ Upstream
Commit: 6fde3fcdfec438ba0df26e25a8ac7c3707211799
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6fde3fcdfec438ba0df26e25a8ac7c3707211799
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74274
Analysis date: Sat, 15 Aug 2026 09:28:24 -0400
ActionableScore: 2
ActionableScore lower bound: 1
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
A NULL hole in the CXL region target array can be left during auto-discovery and later dereferenced during region attach, causing a local privileged or firmware-mediated kernel crash rather than a demonstrated privilege escalation.

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

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

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-74274	LOW	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:N/I:L/A:H';**CWE-476;CWE-665;CWE-703;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.3';DESCR 'CXL region auto discovery can leave NULL holes in the region target array after an endpoint decoder is removed from a non tail slot. Later auto attach may append a decoder after p nr_targets instead of filling the first free slot, while other CXL region code assumes the first p nr_targets entries are valid. This can trigger a NULL pointer dereference during region attach or discovery and can also cause the driver to count a NULL slot as an attached target. For the CVSS the PR:L is used in the paranoid score because some deployments may delegate CXL device management to a service account, container root, or reduced capability administrator rather than requiring full host administrator control. The issue is not network reachable and requires local control over CXL region state or a specific CXL hotplug and auto discovery sequence. Impact is mainly denial of service through a kernel fault or broken CXL region discovery, with only limited integrity concern from incorrect region assembly state.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 2)  SKIP CVE-2026-74274 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: 87805c32e6ad7b5ce2d9f7f47e76081857a4a335 YES  NO NO unknown 	MAYBE	OOB DANGER ERRORPATH UAF HARDWARE  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	-	-	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

Conservative signals:

* Reliable kernel crash / strong DoS: +1
  The commit includes a concrete Oops / general protection fault path through `cxl_calc_interleave_pos()` during CXL region attach / discovery.
* Requires admin/root/CAP-level or privileged device-management control in typical deployments: -2
  Practical triggering generally requires CXL region management, CXL device hotplug / discovery control, or privileged platform/device administration.
* Rare AND difficult-to-reach subsystem/configuration: -1
  CXL region auto-discovery with locked endpoint decoder state is a specialized hardware and configuration-dependent path.

Conservative result is treated as 1 rather than below zero because the patch documents a real kernel crash in a privileged device-management path.

Paranoid additional interpretation:

* Firmware-mediated external influence: +1
  CXL topology, decoder state, and auto-discovery can be influenced by platform firmware or device state, but this is not equivalent to remote network reachability.
* Weak / indirect corruption candidate: +1
  The bug creates an invalid target-array invariant where a NULL slot is counted as an attached endpoint decoder. This is state corruption, but the demonstrated primitive is NULL dereference / bad accounting, not UAF, OOB write, object replacement, or arbitrary write.
* Hard / special conditions: -1
  The problematic state requires endpoint decoder removal from a non-tail slot and later auto-attach / re-discovery behavior.

No strong memory corruption score is awarded. The patch shows a NULL pointer hole and driver state inconsistency, not attacker-controlled reclaim, stale object reuse, write-after-free, type confusion, refcount takeover, or controlled overwrite.

## 3. Reachability analysis

The realistic trigger is local and privileged, or depends on platform / CXL device-management events. A normal unprivileged local user is not expected to control CXL region auto-discovery or endpoint decoder removal. Containers and namespaces do not normally expose this path unless a management service or reduced-capability administrator is delegated control over CXL devices. The path is not network reachable. Exposure is limited to systems with CXL hardware and relevant auto-assembly / locked-decoder behavior.

Call-site confidence: high. The commit provides the affected function, the invalid invariant, and a concrete crash stack through CXL region attach / discovery.

## 4. Severity interpretation

This behaves more like an ordinary Moderate or Low-like kernel robustness issue than an Important-class vulnerability. The theoretical concern is that invalid CXL region state may cause incorrect region assembly or a kernel crash, but the demonstrated impact is NULL pointer dereference and device-management failure. There is no supported privilege escalation primitive, no confidentiality exposure, and no strong integrity corruption beyond limited driver state inconsistency.

## 5. One-sentence report phrase

A NULL hole in the CXL region target array can be left during auto-discovery and later dereferenced during region attach, causing a local privileged or firmware-mediated kernel crash rather than a demonstrated privilege escalation.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

This can be handled as ordinary Moderate / Low-like unless the affected product exposes CXL region management to reduced-privilege users or has additional evidence of UAF, stale pointer reuse, or attacker-controlled memory corruption.

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

Patch: cxl/region: Fill first free targets[] slot during auto-discovery [ Upstream
Commit: 6fde3fcdfec438ba0df26e25a8ac7c3707211799
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6fde3fcdfec438ba0df26e25a8ac7c3707211799

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=6fde3fcdfec438ba0df26e25a8ac7c3707211799

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

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

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:N/I:L/A:H
  The Best / paranoid CVSS score: 5.3

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