[CVE-2026-80684][MODERATE REGULAR] KVM: s390: pci: Fix NULL dereference on AIBV allocation failure

[CVE-2026-80684][MODERATE REGULAR] KVM: s390: pci: Fix NULL dereference on AIBV allocation failure

[AL-KERNEL]

CVE: CVE-2026-80684
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: KVM: s390: pci: Fix NULL dereference on AIBV allocation failure
Commit: 96099486b63985801c9c6ef22505e9aa635b2d20
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=96099486b63985801c9c6ef22505e9aa635b2d20
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80684
Analysis date: Fri, 28 Aug 2026 06:58:10 -0400
ActionableScore: 4
ActionableScore lower bound: 3
Actionable bucket: Borderline manual review recommended, below Important by current evidence
Manual review required: YES

Summary:
No one-sentence report phrase was found.

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

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

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 REGULAR
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-80684	MODERATE	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:C/C:N/I:N/A:H';**CWE-476;CWE-252;CWE-703;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.6';DESCR 'KVM/s390 PCI interrupt forwarding can hit a NULL pointer dereference when airq_iv_create fails and zdev aibv remains NULL before kvm_zpci_set_airq uses it. The practical trigger requires a KVM s390 environment with zPCI forwarding or passthrough and an allocation failure during AIBV setup, so AC:H is appropriate. For the CVSS the PR:L value is used because a local VM management context or a guest context with an assigned zPCI device may be enough in practical deployments, and this should not be treated as full host administrator privileges by default. The issue is not directly network reachable. Impact is denial of service via host kernel crash. No confidentiality or integrity impact is assigned because the visible primitive is a NULL pointer dereference after allocation failure, not UAF, OOB access, or arbitrary write.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline manual review recommended, below Important by current evidence (with actual score 4)	YES	NULLPTR VIRT INIT NOMEMCHK SIMPLEFIX HARDWARE LINUS 	NO	NO	checked

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

ActionableScore=4
ActionableScoreLower=3

1. ActionableScore
* Conservative score: 3
* Paranoid score: 4
* Final recommended bucket: **Borderline manual review recommended, below Important by current evidence**::

2. Signal breakdown
* Local lower privilege KVM context: +1. The path is local to KVM/s390 zPCI management or a guest/device setup context, not a generic remote network path.
* Reliable kernel crash / strong DoS: +1. The unchecked NULL return from airq_iv_create() can leave zdev->aibv NULL and later be dereferenced in kvm_zpci_set_airq().
* Availability impact realistic: +1. The failure mode is a host kernel NULL dereference, so the availability impact can be system-wide for the host.
* Paranoid additional hypervisor-boundary concern: +1. If a guest or reduced VM management context can cause AIBV setup under memory pressure, this becomes guest-to-host or tenant-to-host availability impact.
* No generic memory corruption: +0. The primitive shown is NULL dereference after allocation failure, not UAF, OOB write, double free, type confusion, or arbitrary write.
* No LPE signal: +0. The patch does not show attacker-controlled reclaim, overwrite, callback control, stale object reuse, or refcount takeover.
* No remote/network reachability: +0. This is not packet-triggered or network-exposed by itself.

3. Reachability analysis
The realistic trigger requires KVM on s390 with zPCI interrupt forwarding or passthrough enabled, and an AIBV allocation failure during setup. In typical deployments, this is reachable through local VM/device management rather than by unauthenticated remote input. A fully privileged host administrator would reduce security relevance, but a reduced VM management account, containerized management service, or guest-associated zPCI context should not automatically be treated as PR:H. The path is configuration and architecture specific, but within affected KVM/s390 environments it is a meaningful host-impact crash condition.

4. Severity interpretation
This behaves like a host DoS bug, not an Important-class memory corruption issue. Theoretical escalation is weak because the only demonstrated primitive is a NULL pointer dereference on allocation failure. Realistic impact is availability loss of the host or KVM environment if the setup path can be reached by a lower privilege VM-management or guest-associated actor. It should not be auto-closed purely as trivial because it crosses a virtualization host-impact boundary, but current evidence does not justify Strong Important.

5. One-sentence report phrase
KVM/s390 zPCI interrupt forwarding can dereference a NULL AIBV pointer after airq_iv_create() allocation failure, allowing a local VM management or guest-associated zPCI context to trigger a host kernel crash under specific setup conditions.

6. Manual review recommendation
MANUAL CHECK REQUIRED.
Reason: KVM host impact and possible guest-to-host availability make this worth manual validation, but scoring should remain below Important unless additional evidence shows UAF, object reuse, arbitrary write, or a practical privilege escalation path.

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

Patch: KVM: s390: pci: Fix NULL dereference on AIBV allocation failure
Commit: 96099486b63985801c9c6ef22505e9aa635b2d20
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=96099486b63985801c9c6ef22505e9aa635b2d20

Commit description:

The airq_iv_create() can return NULL on failure, but the return value was
never checked. If it fails, zdev->aibv will be NULL and fail when
dereferenced in kvm_zpci_set_airq(). Add a NULL check and free the
previously allocated AISB bit and zdev->aisb on failure.

Fixes: 3c5a1b6 ("KVM: s390: pci: provide routines for enabling/disabling interrupt forwarding")
Cc: stable@vger.kernel.org
Reviewed-by: Christian Borntraeger <borntraeger@linux.ibm.com>
Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>
Signed-off-by: Farhan Ali <alifm@linux.ibm.com>
Tested-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:
  arch/s390/kvm/pci.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=96099486b63985801c9c6ef22505e9aa635b2d20

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

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

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:C/C:N/I:N/A:H
  The Best / paranoid CVSS score: 5.6

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: 3
  Paranoid ActionableScore: 4

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 REGULAR

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