[CVE-2026-74273][MODERATE 7.0] cxl/region: Block region delete during region creation [ Upstream

[CVE-2026-74273][MODERATE 7.0] cxl/region: Block region delete during region creation [ Upstream

[AL-KERNEL]

CVE: CVE-2026-74273
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: cxl/region: Block region delete during region creation [ Upstream
Commit: b0b6a9c65cb72c901fdcc6ae83d7afd70cdca1b8
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b0b6a9c65cb72c901fdcc6ae83d7afd70cdca1b8
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74273
Analysis date: Sat, 15 Aug 2026 15:55:29 -0400
ActionableScore: 5
ActionableScore lower bound: 3
Actionable bucket: Strong Important candidate / Actionable Moderate at minimum
Manual review required: YES

Summary:
No one-sentence report phrase was found.

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

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

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-74273	MODERATE	CHECK WITH IMPACT FROM ORIG NN LOW	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-362;CWE-667;*CWE-416;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7';DESCR 'A race in CXL region management can allow userspace driven region deletion while region creation or autodiscovery is still completing. The unsafe window is between construct_region() and attach_target(), and also between device_add() and registration of remove actions. This can violate the assumption that struct cxl_region remains registered and live during cxl_add_to_region(), which makes the bug a lifecycle race and a possible use-after-free candidate. For the CVSS the PR:L is used for the paranoid score because some deployments may delegate CXL management to a reduced capability administrator or service account rather than full host root. The issue is local control plane only and is not network reachable. Impact is at least local denial of service via kernel crash, and in the worst defensible case may include confidentiality or integrity impact due to memory corruption.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Strong Important candidate / Actionable Moderate at minimum (with actual score 4)	YES	OOB LOCK INIT SIMPLEFIX HARDWARE  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	YES	NO	checked

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

ActionableScore=5
ActionableScoreLower=3

1. ActionableScore
* Conservative score: 3
* Paranoid score: 5
* Final recommended bucket: **Strong Important candidate / Actionable Moderate at minimum**::

2. Signal breakdown
* Firmware-mediated external influence: +1. The affected path is CXL region creation/autodiscovery, where device topology and hotplug-like flows can influence region construction, but this is not network reachable.
* Memory corruption, weak/indirect corruption candidate: +1. The patch protects a window where a `struct cxl_region` may disappear while creation continues, making this a lifecycle/UAF candidate rather than a proven controlled UAF primitive.
* Real lifetime corruption: +1. The commit explicitly says deletion can violate the assumption that the region stays registered and live through `cxl_add_to_region()` and `devm_add_action_or_reset()`.
* Reliable kernel crash / strong DoS: +1. A stale or disappearing region object in CXL device-management code can realistically crash or destabilize the kernel.
* Privileged kernel/device-management memory corruption path: +1. The bug is in CXL region/device lifecycle management, a trusted kernel device-management path.
* Hard or unreliable race / special timing required: -1. Exploitation depends on racing deletion against region construction or autodiscovery.
* Requires admin/root/CAP-like access in typical deployments: -2 conservative. CXL region create/delete sysfs operations are normally administrator-controlled.
* Privilege penalty refinement for paranoid score: 0 instead of -2. Some deployments may delegate CXL management to a reduced-capability service account, container root, or operator role, so this should not be treated as equivalent to full host-root in the paranoid score.

3. Reachability analysis
The likely trigger is local userspace with permission to create or delete CXL regions through the CXL sysfs control plane while region creation or autodiscovery is in progress. It is not remotely network reachable. Namespaces do not normally make CXL region management available to an unprivileged user, but delegated management or reduced-root operational models can lower the practical privilege barrier. The path is only relevant on systems with CXL hardware and enabled CXL region management, but when present it is an ordinary device-management interface rather than a purely theoretical code path. Call-site confidence: high, because the patch shows the create, delete, and `cxl_add_to_region()` locking changes directly.

4. Severity interpretation
This is stronger than an ordinary Moderate correctness fix because it protects object lifetime during a region creation/deletion race. Realistic impact is most likely local DoS through kernel crash or device-management state corruption. Theoretical memory corruption risk exists because the patch explicitly prevents operations on a region that may no longer be live, but there is no demonstrated attacker-controlled reclaim, write-after-free, callback control, or type confusion. Therefore the conservative score remains borderline, while the paranoid score is Actionable Moderate and should not be auto-closed.

5. One-sentence report phrase
A race in CXL region management can allow userspace driven region deletion while creation or autodiscovery is still completing, leaving kernel code operating on a region object whose lifetime assumptions may no longer hold and causing at least a local DoS with possible lifecycle memory corruption.

6. Manual review recommendation
MANUAL CHECK REQUIRED.
Reason: the patch protects a real object-lifetime window involving `struct cxl_region`, `device_add()`, `attach_target()`, and devm cleanup registration. Even though a practical LPE primitive is not demonstrated, the lifecycle/UAF candidate in privileged CXL device-management code warrants manual review.

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

Patch: cxl/region: Block region delete during region creation [ Upstream
Commit: b0b6a9c65cb72c901fdcc6ae83d7afd70cdca1b8
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b0b6a9c65cb72c901fdcc6ae83d7afd70cdca1b8

Changed files:
  drivers/cxl/core/port.c
  drivers/cxl/core/region.c
  drivers/cxl/cxl.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=b0b6a9c65cb72c901fdcc6ae83d7afd70cdca1b8

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

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

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: 3
  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: NO
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).