[CVE-2026-80548][MODERATE 7.0] s390/vfio_ccw: Selectively expand io_mutex

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

CVE: CVE-2026-80548
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: s390/vfio_ccw: Selectively expand io_mutex
Commit: f72a51810d49411bd8cad0c2df8592320a2fe5cc
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f72a51810d49411bd8cad0c2df8592320a2fe5cc
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80548
Analysis date: Wed, 26 Aug 2026 13:45:36 -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 can allow a local process with delegated VFIO device access to race channel-program teardown against I/O completion or inspection paths, causing possible stale object access and kernel crash, with paranoid concern for broader memory-corruption impact.

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

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

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-80548	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-416;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 'vfio_ccw has a race around the channel program lifecycle because cp_free and other I/O paths were not consistently serialized by io_mutex. A local process with access to the vfio_ccw device may race I/O completion, close, notoper cleanup, CRW handling, or pinned IOVA checks against channel program teardown. This can result in use after free or list corruption in kernel I/O structures and at minimum can crash the kernel. For the CVSS the PR:L is used because reliable triggering requires a local user or service process with access to the VFIO device, but it does not necessarily require full host administrator privileges when VFIO access is delegated to a VM process or reduced capability service account. The issue is not network reachable. Impact is at least local denial of service and in the paranoid case may allow confidentiality or integrity impact due to kernel memory corruption, 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	LOCK DANGER SIMPLEFIX RACE HARDWARE LINUS  DECREASED_TO_MODERATEREG_BASED_ON_FALSEPOSCHECKOFKP	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

Triggered signals:

* Local unprivileged or reduced-privilege trigger: +1
  A fully unprivileged user normally cannot access vfio_ccw, but a VM process, service account, or delegated VFIO user may have access without full host-root privileges.

* Memory corruption, weak or indirect corruption candidate: +1
  The patch serializes `cp_free()`, `cp_update_scsw()`, `cp_iova_pinned()`, CRW handling, and I/O completion paths. This indicates possible stale traversal or update of channel-program structures, but no controlled reclaim or write primitive is shown.

* Real lifetime corruption: +1
  The changed locking explicitly protects the `cp` lifecycle, including paths where `cp_free()` can race with users of `ccwchain_list` and related I/O resources.

* Reliable kernel crash / strong DoS: +1
  A race in VFIO channel-program teardown or completion handling can plausibly crash the kernel through stale list/object access.

* Privileged kernel/device-management memory corruption path: +1
  The affected code is in `s390/vfio_ccw`, a trusted device passthrough and I/O-management path.

Subtract / limiting signals:

* Hard or unreliable race / special timing required: -1
  The issue depends on racing I/O completion, close, notoper cleanup, CRW handling, or pinned-IOVA checks against channel-program teardown.

Not awarded:

* Strong LPE plausibility: +0
  No attacker-controlled reclaim, controlled overwrite, callback dispatch, refcount takeover, or type confusion is demonstrated.

* Remote reachable: +0
  This is not network-triggerable.

* Confidentiality / integrity impact in conservative score: +0
  The conservative evidence supports stale lifetime corruption and crash risk, but not a concrete read/write primitive.

Paranoid interpretation:

* Paranoid score is raised to 5 because this is a kernel race around object lifetime in VFIO I/O structures. Even without a demonstrated exploit primitive, UAF/list corruption in a delegated device-access context should not be auto-closed.

## 3. Reachability analysis

The likely trigger is a local process with access to a `vfio_ccw` device on s390, typically a VM/VFIO management process. In default systems this requires administrative setup, but after delegation the triggering process may not have full host-root privileges. Containers and reduced-capability service accounts matter because VFIO access can be granted to a non-root or partially privileged process. The path is hardware and configuration dependent, so exposure is narrower than generic local kernel APIs. Realistic exploitation requires access to s390 vfio_ccw passthrough plus race timing against I/O lifecycle events.

## 4. Severity interpretation

This is above ordinary Moderate because the patch expands locking around `cp` lifecycle and I/O resource ownership, which strongly suggests a real lifetime race. Realistic impact is most clearly local kernel crash or host DoS. Theoretical privilege escalation is possible only as a paranoid concern because kernel UAF/list corruption can sometimes be exploitable, but the patch does not show controlled reclaim, arbitrary write, callback control, or a demonstrated LPE path. Therefore this is best treated as Actionable Moderate at minimum, with manual review recommended for Important-class consideration.

## 5. One-sentence report phrase

A race in s390 vfio_ccw can allow a local process with delegated VFIO device access to race channel-program teardown against I/O completion or inspection paths, causing possible stale object access and kernel crash, with paranoid concern for broader memory-corruption impact.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: this is a race involving kernel object lifetime and `cp_free()` synchronization in a VFIO device-management path. The conservative impact is DoS, but the UAF/list-corruption shape and delegated-device-access model make it unsafe to auto-close without human review.

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

Patch: s390/vfio_ccw: Selectively expand io_mutex
Commit: f72a51810d49411bd8cad0c2df8592320a2fe5cc
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f72a51810d49411bd8cad0c2df8592320a2fe5cc

Commit description:

The io_mutex was defined to serialize the io_regions, but then has
also sort of been associated with the I/O themselves because of
the close relationship they share.

With the handful of races that are possible, the choices are either to:
 A) expand the scope of io_mutex to close these remaining windows, or
 B) reduce the scope of io_mutex to just io_region, and introduce a new
    lock mechanism for the remaining I/O resources

This patch implements A, since B brings with it a lot more interactions
that would need to be tracked and kept in a correct hierarchy. It also
takes advantage of the workqueue element for cp_free() that now gets
called out of fsm_notoper(), which could be invoked out of an interrupt
context and thus cannot acquire a mutex itself.

Fixes: 4f76617 ("vfio-ccw: protect the I/O region")
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_chp.c
  drivers/s390/cio/vfio_ccw_cp.c
  drivers/s390/cio/vfio_ccw_drv.c
  drivers/s390/cio/vfio_ccw_fsm.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=f72a51810d49411bd8cad0c2df8592320a2fe5cc

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

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

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