[CVE-2026-80640][LOW] cxl/fwctl: Fix __fortify_panic [ Upstream

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

CVE: CVE-2026-80640
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: cxl/fwctl: Fix __fortify_panic [ Upstream
Commit: b8d15e85596ad8993d42e0703a9741961a2f03eb
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b8d15e85596ad8993d42e0703a9741961a2f03eb
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80640
Analysis date: Fri, 28 Aug 2026 04:03:17 -0400
ActionableScore: 1
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
A CXL/fwctl supported features request can trigger a FORTIFY assertion because num_entries is initialized after filling a counted array, causing a local denial of service on systems where the CXL fwctl interface is accessible.

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

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

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-80640	LOW	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';CWE-665;CWE-617;CWE-703;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.5';DESCR 'A runtime assertion in CXL/fwctl can be triggered in cxlctl_get_supported_features because num_entries is initialized after the code starts filling the counted entries array. FORTIFY treats the __counted_by_le(num_entries) array size as 0 and reports a 48 byte write into a 0 byte buffer, resulting in __fortify_panic or a warning based crash condition. For the CVSS the PR:L is used for the paranoid score because fwctl or CXL management access may be delegated to a local service account or reduced capability administrator, although normal deployments usually restrict it to root. The issue is not network reachable and is a local control plane problem on systems with CXL fwctl support enabled. Impact is denial of service only. The patch context indicates a FORTIFY false positive rather than a real buffer overflow, so no confidentiality or integrity impact is assigned.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)  SKIP CVE-2026-80640 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	OOB DANGER SIMPLEFIX HARDWARE  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	-	-	checked

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

ActionableScore=1
ActionableScoreLower=0

## 1. ActionableScore

* Conservative score: 0
* Paranoid score: 1
* Final recommended bucket: **Ordinary Moderate / Low-like**

## 2. Signal breakdown

* Reliable kernel crash / strong DoS: +1
  `__fortify_panic` or warning based crash is described in the commit trace when `cxlctl_get_supported_features()` is called.

* Requires admin/root/CAP_* in typical deployments: -2
  CXL fwctl and CXL device management paths are normally administrator controlled.

* Rare AND difficult-to-reach subsystem/configuration: -1
  Requires CXL hardware/support and the newer CXL fwctl feature command path.

* Paranoid privilege refinement: +1 instead of full admin-only dismissal
  In some environments CXL management access could be delegated to a reduced capability service account, so the paranoid interpretation treats this as locally triggerable by a less-than-full-root actor.

No memory corruption signal is awarded. The patch explicitly describes this as a FORTIFY false positive caused by late initialization of `num_entries` for a counted flexible array. The allocation size is already derived from `requested`, and the fix only moves the counter initialization before filling the array.

## 3. Reachability analysis

The bug is local and requires access to the CXL fwctl control plane. It is not network reachable. Namespaces and containers do not normally expose this interface to unprivileged users, but a management service or reduced capability administrator could potentially reach it if device control is delegated. The path is not default-reachable on ordinary systems because it depends on CXL hardware, CXL fwctl support, and appropriate permissions.

## 4. Severity interpretation

This behaves like an ordinary Moderate or Low-like reliability issue, not an Important-class vulnerability. The realistic impact is local denial of service through a FORTIFY assertion or crash. Theoretical memory corruption is not supported by the patch because the described overflow is a bounds-checking false positive rather than an actual attacker-controlled overwrite. There is no supported confidentiality, integrity, privilege escalation, UAF, OOB write, refcount, or stale pointer primitive.

## 5. One-sentence report phrase

A CXL/fwctl supported features request can trigger a FORTIFY assertion because num_entries is initialized after filling a counted array, causing a local denial of service on systems where the CXL fwctl interface is accessible.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

This can be handled as auto-closable unless the evaluated product delegates CXL fwctl access to untrusted local users. The patch context supports DoS only and does not show a real memory corruption primitive.

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

Patch: cxl/fwctl: Fix __fortify_panic [ Upstream
Commit: b8d15e85596ad8993d42e0703a9741961a2f03eb
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b8d15e85596ad8993d42e0703a9741961a2f03eb

Changed files:
  lib/string_helpers.c
  drivers/cxl/core/features.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=b8d15e85596ad8993d42e0703a9741961a2f03eb

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

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

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

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