[CVE-2026-80547][MODERATE 7.0] s390/vfio_ccw: Implement a crw lock

[CVE-2026-80547][MODERATE 7.0] s390/vfio_ccw: Implement a crw lock

[AL-KERNEL]

CVE: CVE-2026-80547
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: s390/vfio_ccw: Implement a crw lock
Commit: 49fa26b0df009dc1f420980bd71780e70615b83b
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=49fa26b0df009dc1f420980bd71780e70615b83b
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80547
Analysis date: Wed, 26 Aug 2026 13:04:08 -0400
ActionableScore: 5
ActionableScore lower bound: 4
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
A race in s390 vfio_ccw CRW handling allows asynchronous hardware event paths and userspace read or release paths to access the same CRW list without locking, potentially causing list corruption, stale-object access, and host kernel denial of service.

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

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

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-80547	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:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7';DESCR 'A race condition exists in s390 VFIO/CCW CRW handling because the private CRW list is accessed from asynchronous hardware event paths and from userspace read or device release paths without a dedicated lock. Concurrent list_add_tail, list_del, list traversal, kfree, and eventfd signaling can expose list corruption or use-after-free-like behavior, with the most direct impact being a host kernel crash. For the CVSS the PR:L is used for the paranoid score because triggering requires a local process with access to the VFIO/CCW mediated device, while full device setup may still require administrator action. The issue is not network reachable and is specific to s390 systems using vfio_ccw. Impact is at least local denial of service, and in the worst case may allow confidentiality or integrity impact due to kernel list memory corruption, so it should be reviewed manually.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 5)	YES	LOCK DANGER INIT SIMPLEFIX 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: **Actionable Moderate at minimum**

## 2. Signal breakdown

Triggered signals:

* Local privileged or delegated-device trigger: +1
  Triggering requires a local userspace process with access to the vfio_ccw mediated device or its VFIO region. This is not ordinary remote reachability, but it is also not equivalent to full host-root once the device is delegated.

* Firmware-mediated or hardware-event influence: +1
  The CRW queue is populated from asynchronous channel-report events coming from hardware. This is better modeled as firmware or hardware mediated influence, not as direct network reachability.

* Memory corruption, weak or indirect corruption candidate: +1
  The patch protects concurrent `list_add_tail`, `list_first_entry_or_null`, `list_del`, list traversal, and `kfree` on `private->crw`. This is an unlocked kernel list race and can plausibly cause list corruption or stale-object access, but the patch does not show attacker-controlled reclaim, overwrite, type confusion, or callback control.

* Real lifetime corruption: +1
  The race includes deletion and freeing of `struct vfio_ccw_crw` objects while other paths can inspect or manipulate the same list.

* Reliable kernel crash or strong DoS: +1
  Concurrent list mutation and freeing can realistically produce host kernel crash or corrupted list state.

Subtracting signals:

* Hard or timing-dependent race: -1
  Exploitation depends on overlap between asynchronous CRW production, userspace reads, event notification, and device release or cleanup paths.

* Rare architecture and subsystem exposure: -1
  This is specific to s390 systems using vfio_ccw mediated devices, not a broad default Linux path.

Conservative total: 4
Paranoid total: 5

No additional LPE bonus is awarded. The patch supports a race and possible lifetime/list corruption, but does not show controlled reclaim, writable UAF reuse, type confusion, callback dispatch, refcount takeover, or arbitrary write.

## 3. Reachability analysis

The bug is local and device-specific. A realistic trigger requires an s390 host with vfio_ccw enabled and a mediated device exposed to a userspace VMM or management process. Full setup of vfio_ccw devices is normally administrative, but once a VFIO device is delegated, the process using it may run with reduced privileges rather than full host-root.

The path is not network reachable. A guest or VMM workload may influence timing indirectly through device activity and CRW delivery, but the commit does not demonstrate a direct guest-to-host exploit primitive. Containers and namespaces do not normally make this broadly reachable unless the VFIO device node or management interface is intentionally delegated.

Call-site confidence: high. The patch shows enqueue, dequeue, event notification, and release cleanup paths for the same list.

## 4. Severity interpretation

This behaves above an ordinary Moderate because it is an unlocked kernel list lifetime race involving list deletion and `kfree` in a privileged device virtualization path. The realistic impact is host kernel DoS. The theoretical concern is memory corruption from stale list entries or concurrent free, but practical privilege escalation is not demonstrated.

Conservative handling is borderline manual review. Paranoid handling is Actionable Moderate because kernel list lifetime corruption in VFIO device code should not be auto-closed without review.

## 5. One-sentence report phrase

A race in s390 vfio_ccw CRW handling allows asynchronous hardware event paths and userspace read or release paths to access the same CRW list without locking, potentially causing list corruption, stale-object access, and host kernel denial of service.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: this is a synchronization fix for an asynchronously updated kernel list that is also dequeued and freed. Even though direct LPE is not proven, the lifetime/list-corruption pattern is strong enough to require manual review.

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

Patch: s390/vfio_ccw: Implement a crw lock
Commit: 49fa26b0df009dc1f420980bd71780e70615b83b
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=49fa26b0df009dc1f420980bd71780e70615b83b

Commit description:

Unlike the channel_program struct, which covers synchronous I/O
submissions and asynchronous interrupts, the CRW region relies
exclusively on asynchronous events coming from hardware.

Implement a lock to manage the list of those payloads, to ensure
they are read cohesively.

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>
Reviewed-by: Farhan Ali <alifm@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_chp.c
  drivers/s390/cio/vfio_ccw_drv.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=49fa26b0df009dc1f420980bd71780e70615b83b

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

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

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