[CVE-2026-80553][MODERATE 7.0] s390/vfio_ccw: Cancel existing workqueues

[CVE-2026-80553][MODERATE 7.0] s390/vfio_ccw: Cancel existing workqueues

[AL-KERNEL]

CVE: CVE-2026-80553
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: s390/vfio_ccw: Cancel existing workqueues
Commit: e868ea8be0bc88c6982f48ecf3259d98afd884ae
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e868ea8be0bc88c6982f48ecf3259d98afd884ae
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80553
Analysis date: Wed, 26 Aug 2026 11:00:11 -0400
ActionableScore: 5
ActionableScore lower bound: 4
Actionable bucket: Strong Important candidate / Actionable Moderate at minimum
Manual review required: YES

Summary:
A race in s390 vfio_ccw device close or release handling can allow pending io_work or crw_work to run after vfio_ccw_private is freed, causing a host kernel use after free and at least a local DoS, with manual review warranted for possible but unproven broader memory corruption impact.

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

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

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-80553	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-416;CWE-362;CWE-667;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7';DESCR 's390 vfio_ccw can leave io_work or crw_work pending while the vfio_ccw_private object is closed or released. A delayed work item may then run after the private object has been freed, creating a race based use after free in the host kernel. For the CVSS the PR:L is used for the paranoid score because access to VFIO devices can be delegated to a non root service account, container root, or a user with device access rather than requiring full host administrator privileges. The issue is not network reachable and requires local host access or a delegated VFIO control path. Impact is at least local denial of service via kernel crash and in the worst case may allow confidentiality or integrity impact due to kernel use after free, so it should be reviewed manually.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Strong Important candidate / Actionable Moderate at minimum (with actual score 5)	YES	SIMPLEFIX HARDWARE LINUS  KPANIC INCREASED_TO_MODERATE_FROM_LOW_BASED_ON_GUESSCVSS	NO	NO	checked

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

ActionableScore=5
ActionableScoreLower=4

## 1. ActionableScore

* Conservative score: 4
* Paranoid score: 5
* Final recommended bucket: **Strong Important candidate / Actionable Moderate at minimum**::

## 2. Signal breakdown

* Local delegated VFIO trigger: +1
  The bug is reachable through local VFIO mediated device close or release paths when access to the vfio-ccw device is delegated to QEMU, a service account, container root, or another reduced-privilege user.

* Memory corruption, weak primitive: +1
  This is a race-dependent UAF lifetime bug. The patch prevents queued io_work or crw_work from running after vfio_ccw_private is released, but there is no demonstrated attacker-controlled reclaim, overwrite, type confusion, or callback control.

* Real lifetime corruption: +1
  The private object can be freed while asynchronous work items still reference it.

* Reliable kernel crash / strong DoS: +1
  A work item firing after object release can plausibly dereference freed kernel memory and crash the host kernel.

* Privileged kernel/device-management memory corruption path: +1 for paranoid score
  The bug is in VFIO device lifecycle handling, a trusted host device-management path. This justifies manual-review elevation, but not confirmed LPE.

* Race-UAF downgrade rule applied
  No extra LPE bonus is awarded because the patch does not show controlled reclaim, write-after-free, type confusion, refcount takeover, or function pointer control.

* No remote/network signal
  The issue is not network reachable.

* No rare-subsystem penalty applied for the main score
  s390 vfio-ccw is platform-specific, but on affected s390 virtualization deployments it is reachable through ordinary VFIO device lifecycle operations.

## 3. Reachability analysis

A local actor with access to the vfio-ccw mediated device lifecycle can potentially trigger the vulnerable close or release path while io_work or crw_work is pending. In typical deployments, full device creation and assignment may require administrator involvement, but actual device access can be delegated to a non-root QEMU process, service account, container root, or user with VFIO device permissions. Namespaces and containerization can therefore lower the practical privilege interpretation from full host root to PR:L-like delegated access. The path is not default-reachable on all systems and is specific to s390 vfio-ccw usage, but it is security-relevant for affected virtualization hosts.

## 4. Severity interpretation

This behaves more like an Actionable Moderate issue than an ordinary Moderate cleanup because it fixes a real async workqueue lifetime UAF in a host VFIO device path. The realistic demonstrated impact is local host kernel crash or DoS. The theoretical worst case includes broader kernel memory corruption impact, but the patch does not show a strong exploit primitive such as controlled reclaim, arbitrary write, type confusion, or callback hijack. Therefore the conservative score is capped at 4 and the paranoid score is capped at 5 under the race-UAF downgrade rule.

## 5. One-sentence report phrase

A race in s390 vfio_ccw device close or release handling can allow pending io_work or crw_work to run after vfio_ccw_private is freed, causing a host kernel use after free and at least a local DoS, with manual review warranted for possible but unproven broader memory corruption impact.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: this is a real UAF lifetime bug in a VFIO host device-management path, and access may be delegated below full host-root privileges even though no strong LPE primitive is demonstrated.

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

Patch: s390/vfio_ccw: Cancel existing workqueues
Commit: e868ea8be0bc88c6982f48ecf3259d98afd884ae
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e868ea8be0bc88c6982f48ecf3259d98afd884ae

Commit description:

The initialization of the io_work and crw_work workqueues begs the
question of whether they should be un-initialized. Add the corresponding
cleanup tags in _release_dev to ensure work isn't dispatched after
the private struct is free'd.

Suggested-by: Matthew Rosato <mjrosato@linux.ibm.com>
Fixes: e5f84db ("vfio: ccw: return I/O results asynchronously")
Fixes: 3f02cb2 ("vfio-ccw: Wire up the CRW irq and CRW region")
Cc: stable@vger.kernel.org
Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>
Signed-off-by: Eric Farman <farman@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_ops.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=e868ea8be0bc88c6982f48ecf3259d98afd884ae

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

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

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:L/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: 4
  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: YES
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).