[CVE-2026-45981][MODERATE REGULAR] s390/cio: Fix device lifecycle handling in css_alloc_subchannel() [ Upstream

[CVE-2026-45981][MODERATE REGULAR] s390/cio: Fix device lifecycle handling in css_alloc_subchannel() [ Upstream

[AL-KERNEL]

CVE: CVE-2026-45981
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: s390/cio: Fix device lifecycle handling in css_alloc_subchannel() [ Upstream
Commit: 2b2ad7ad4a28ffdb9f94e6d979b88a5b12b71681
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2b2ad7ad4a28ffdb9f94e6d979b88a5b12b71681
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-45981
Analysis date: Wed, 27 May 2026 08:58:01 -0400
ActionableScore: 3
ActionableScore lower bound: 2
Actionable bucket: Borderline, manual review recommended
Manual review required: YES

Summary:
No one-sentence report phrase was found.

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

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

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-45981	MODERATE	CHECK	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H';*CWE-672;*CWE-416;CWE-415;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.2';DESCR 's390 cio css_alloc_subchannel frees a subchannel with kfree after device_initialize when DMA mask setup fails, bypassing the device model reference lifetime rules. This creates a weak lifetime corruption candidate because the embedded struct device should be released through put_device and its release callback rather than direct free. For the CVSS the PR:H is used even for the paranoid case because triggering this path normally requires privileged device management or rare s390 channel device initialization failure conditions, not ordinary local user access. The issue is not network reachable and is tied to s390 CIO device probing or recovery paths. Impact is mainly availability, with limited confidentiality and integrity concern only in the paranoid interpretation due to potential use after free or double free.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline, manual review recommended (with actual score 3)	YES	DANGER ERRORPATH UAF DMAorINTERRUPT HARDWARE LINUS  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH	NO	NO	checked

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

ActionableScore=3
ActionableScoreLower=2

1. ActionableScore
* Conservative score: 2
* Paranoid score: 3
* Final recommended bucket: **Borderline, manual review recommended**::

2. Signal breakdown
* Memory corruption, weak/indirect corruption candidate: +1. The patch fixes a device lifetime mismatch after device_initialize(), and the commit explicitly mentions potential use-after-free or double-free.
* Real lifetime corruption: +1. Direct kfree() bypasses device model reference counting and release callback ownership.
* Privileged kernel/device-management memory corruption path: +1. The issue is in s390 CIO subchannel allocation, a trusted device-management path.
* Firmware-mediated or hardware-mediated influence: +1 in paranoid scoring. The failure depends on device/DMA setup conditions rather than ordinary user-controlled input.
* Availability impact plausible: +1. A lifetime mismatch in device probing can plausibly cause crash or unstable device handling.
* Requires privileged or device-management conditions: -2. Reliable triggering normally requires s390 device probing/recovery or administrative/hardware setup, not an ordinary local user.
* Rare hardware / architecture-specific condition: -1 to -2. This is limited to s390 CIO and a DMA mask failure path, making broad exposure low.
* Constrained primitive: -1 in paranoid scoring. There is no attacker-controlled payload, reclaim strategy, arbitrary write, or demonstrated LPE primitive.

3. Reachability analysis
The bug is reachable during s390 channel I/O subchannel allocation when DMA mask setup fails after device_initialize(). It is not network reachable and not reachable through a normal unprivileged syscall path. Containers and user namespaces do not materially reduce the privilege requirement because the affected path is host device initialization or recovery, not namespaced device control. Realistic exploitation requires rare hardware or firmware/device-management failure conditions, so attacker control is weak.

4. Severity interpretation
This behaves more like a low-end Borderline or unusual Moderate issue than an Important-class vulnerability. The theoretical concern is real because the patch fixes a lifetime rule violation that can become UAF or double-free. The realistic exploitation evidence is weak because the path is architecture-specific, error-path-only, and lacks a controlled allocation or overwrite primitive. Manual review is still useful because kernel device lifetime bugs are often under-described and may have hidden crash or double-free behavior.

5. One-sentence report phrase
A s390 CIO error path freed a subchannel directly after device_initialize(), bypassing device model reference counting and creating a potential UAF or double-free during rare device initialization failure conditions.

6. Manual review recommendation
MANUAL CHECK RECOMMENDED
The patch explicitly fixes a potential UAF or double-free, but exposure is narrow and practical attacker control appears weak.

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

Patch: s390/cio: Fix device lifecycle handling in css_alloc_subchannel() [ Upstream
Commit: 2b2ad7ad4a28ffdb9f94e6d979b88a5b12b71681
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2b2ad7ad4a28ffdb9f94e6d979b88a5b12b71681

Changed files:
  drivers/s390/cio/css.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=2b2ad7ad4a28ffdb9f94e6d979b88a5b12b71681

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

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

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

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

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