[CVE-2026-80549][LOW] s390/vfio_ccw: Move cp cleanup out of not operational

[CVE-2026-80549][LOW] s390/vfio_ccw: Move cp cleanup out of not operational

[AL-KERNEL]

CVE: CVE-2026-80549
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: s390/vfio_ccw: Move cp cleanup out of not operational
Commit: f98a9890ca42f4223d2d4c50e0660af3e012fcb4
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f98a9890ca42f4223d2d4c50e0660af3e012fcb4
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80549
Analysis date: Wed, 26 Aug 2026 11:42:42 -0400
ActionableScore: 1
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
s390 vfio_ccw could clean up channel program resources from an asynchronous not-operational device-loss path while other locks are held, creating a low-confidence host availability risk in specialized VFIO CCW virtualization deployments.

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

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

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-80549	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:N/A:H';CWE-667;*CWE-833;*CWE-664;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.7';DESCR 'vfio_ccw may free channel program resources from the not-operational state while the asynchronous device loss path is running under other locks such as the cio subchannel lock. This creates a lock context and ordering risk that can affect host availability if cleanup runs in the wrong call chain. For the CVSS the PR:L is used for the paranoid score because a local VM process or service account with access to the vfio_ccw mediated device may be sufficient in delegated virtualization setups. The issue is not network reachable and does not show a concrete memory corruption primitive. Impact is denial of service through a possible host side hang or cleanup failure rather than confidentiality or integrity compromise.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)	YES	LOCK DANGER INIT HARDWARE LINUS  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	YES	NO	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

Conservative signals:

* Availability concern: +1. The old path could call `cp_free(&private->cp)` from `fsm_notoper()` while the asynchronous not-operational path may already hold locks such as the CIO subchannel lock.
* Requires admin or privileged device setup in typical deployments: -2. Practical access normally requires s390 `vfio_ccw`, mediated device setup, and a VM or management process already authorized to use that device.
* No concrete memory corruption primitive: +0. The patch moves cleanup to a workqueue and flushes it on close and release, but does not show UAF, double free, OOB access, stale callback, refcount takeover, or attacker-controlled reuse.

Paranoid additional interpretation:

* Firmware or device-mediated asynchronous influence: +1. The not-operational transition can be caused by device loss or subchannel events outside the normal driver flow, but this is not a remotely network-triggerable path.
* Hard or unreliable condition: -1. Triggering depends on an asynchronous device-loss path and a problematic lock context, not a simple deterministic userspace operation.

Call-site confidence: high. The patch shows the direct caller change in `fsm_notoper()`, the new `notoper_work`, and the close/release flushing paths.

## 3. Reachability analysis

The bug is local and platform-specific. It affects s390 `vfio_ccw` mediated device usage, typically in virtualization environments. A normal unprivileged local user cannot usually create or control this path without prior access to a configured VFIO CCW device or a VM process authorized by the host. Namespace or container delegation could reduce the practical privilege level to a service account or reduced-capability VM process, but it still does not become a generic unprivileged local kernel API. The issue is not network reachable.

## 4. Severity interpretation

This behaves like a low-end Moderate or Low-like availability issue, not an Important-class vulnerability. The patch addresses cleanup being performed in an unsafe lock context by deferring `cp_free()` to a workqueue. There is no demonstrated memory corruption primitive, no confidentiality impact, no integrity impact, and no plausible privilege escalation path from the supplied patch. The realistic impact is host-side DoS or hang risk in a narrow s390 VFIO CCW device-loss scenario.

## 5. One-sentence report phrase

s390 vfio_ccw could clean up channel program resources from an asynchronous not-operational device-loss path while other locks are held, creating a low-confidence host availability risk in specialized VFIO CCW virtualization deployments.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

The issue is narrow, non-network-reachable, platform-specific, and does not show a concrete memory corruption or privilege escalation primitive. It can be handled as a low-priority availability fix unless the affected product heavily exposes delegated `vfio_ccw` access to untrusted tenants.

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

Patch: s390/vfio_ccw: Move cp cleanup out of not operational
Commit: f98a9890ca42f4223d2d4c50e0660af3e012fcb4
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f98a9890ca42f4223d2d4c50e0660af3e012fcb4

Commit description:

The fsm_notoper() routine is called when the device has been
lost, and is (by definition) no longer operational. Since this
can happen asynchronously from the normal behavior of the
driver, the cleanup may happen when holding other locks
in the calling sequence (notably, the cio subchannel lock).

Push the cleanup of the private->cp resources to a workqueue,
where it can be done out from under that lock sequence and
a future patch can safely manage the locking requirements.

Fixes: 204b394 ("vfio/ccw: Move FSM open/close to MDEV open/close")
Cc: stable@vger.kernel.org
Signed-off-by: Eric Farman <farman@linux.ibm.com>
Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@linux.ibm.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/s390/cio/vfio_ccw_drv.c
  drivers/s390/cio/vfio_ccw_fsm.c
  drivers/s390/cio/vfio_ccw_ops.c
  drivers/s390/cio/vfio_ccw_private.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=f98a9890ca42f4223d2d4c50e0660af3e012fcb4

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

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

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