[CVE-2026-80679][LOW] s390/dasd: Fix potential NULL pointer dereference

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

CVE: CVE-2026-80679
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: s390/dasd: Fix potential NULL pointer dereference
Commit: dbf2ae34d2f1390a9fc1abf3dce7f809e022caae
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=dbf2ae34d2f1390a9fc1abf3dce7f809e022caae
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80679
Analysis date: Fri, 28 Aug 2026 06:53:47 -0400
ActionableScore: 2
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: YES

Summary:
A NULL pointer dereference in the s390/dasd release_space ioctl path can crash the kernel when a DASD discipline lacks the is_ese() callback, with typical exploitation requiring local DASD device control access.

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

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

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: LOW
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-80679	LOW	CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-754;CWE-703;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.5';DESCR 'A NULL-pointer dereference in the s390/dasd release_space path occurs because dasd_release_space can call the is_ese() discipline callback even when that callback is NULL. A local actor with access to the DASD block device ioctl can trigger a kernel crash when release space handling reaches a device discipline that does not implement is_ese(). For the CVSS the PR:L is used for the paranoid score because delegated block device access or a service account with ioctl access may be enough in some deployments, while full administrator privileges are more typical. The issue is not network reachable and requires local interaction with the DASD device control path. Impact is denial of service via kernel oops or panic only, with no supported confidentiality or integrity impact.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)	YES	NULLPTR SIMPLEFIX HARDWARE  INCREASED_FROM_LOW_BASED_ON_HIGHCVSSSCORE DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5 DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	NO	NO	checked

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

ActionableScore=2
ActionableScoreLower=0

## 1. ActionableScore

* Conservative score: 0
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate / Low-like**::

## 2. Signal breakdown

Conservative scoring:

* Reliable kernel crash / strong DoS: +1. Calling a NULL `is_ese()` discipline callback can cause a kernel oops or panic.
* Requires admin/root/device-management access in typical deployments: -2. Triggering the path normally requires access to DASD block-device ioctls, which is usually restricted.
* Rare hardware/subsystem exposure: -1. This is s390 DASD-specific and not a broad default Linux exposure.
* Result is floored at 0.

Paranoid scoring:

* Local lower-privileged trigger: +1. If a service account, delegated storage-management process, or non-root user has ioctl access to the DASD block device, PR:L is defensible.
* Reliable kernel crash / strong DoS: +1. The bad logical AND can directly call a NULL callback.
* No memory-corruption or LPE bonus. This is a NULL function-pointer/deref crash path, not UAF, OOB write, refcount abuse, type confusion, or controlled overwrite.

## 3. Reachability analysis

The bug is local-only and requires interaction with the s390 DASD release-space ioctl path. It is not network reachable. Namespaces do not materially reduce the requirement unless the actual DASD block device or a management service exposing that ioctl is delegated into a container or to a less privileged account. The affected hardware and subsystem are specialized, so exposure is limited to s390 systems using DASD devices and the release-space feature.

Call-site confidence: medium. The patch shows the vulnerable helper and surrounding ioctl-related file context, but not the full ioctl dispatch path.

## 4. Severity interpretation

This behaves like an ordinary Moderate or Low-like local DoS issue. The realistic impact is kernel crash or oops from a NULL callback call. There is no supported confidentiality or integrity impact, and no evidence of privilege escalation. The paranoid score accounts for delegated local device access, but still does not elevate the bug into Actionable Moderate or Important because the primitive is crash-only.

## 5. One-sentence report phrase

A NULL pointer dereference in the s390/dasd release_space ioctl path can crash the kernel when a DASD discipline lacks the is_ese() callback, with typical exploitation requiring local DASD device control access.

## 6. Manual review recommendation

NO MANUAL CHECK REQUIRED COULD BE AUTOCLOSED

Reason: crash-only NULL pointer dereference, local specialized device path, no memory corruption primitive, no network reachability, and no plausible LPE evidence from the patch.

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

Patch: s390/dasd: Fix potential NULL pointer dereference
Commit: dbf2ae34d2f1390a9fc1abf3dce7f809e022caae
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=dbf2ae34d2f1390a9fc1abf3dce7f809e022caae

Commit description:

dasd_release_space() checks the implementation of the is_ese()
discipline function before calling it to determine if a given device is
an ESE DASD.

The current usage of the logical AND operator will lead to a NULL
pointer dereference as the function is called even if the function
pointer is NULL.

Fix this by using the logical OR operator.

Fixes: 91dc4a1 ("s390/dasd: Add new ioctl to release space")
Cc: stable@vger.kernel.org # v5.3+
Reported-by: Vasily Gorbik <gor@linux.ibm.com>
Acked-by: Eduard Shishkin <edward6@linux.ibm.com>
Reviewed-by: Stefan Haberland <sth@linux.ibm.com>
Signed-off-by: Jan Höppner <hoeppner@linux.ibm.com>
Signed-off-by: Stefan Haberland <sth@linux.ibm.com>
Link: https://patch.msgid.link/20260727142840.567286-3-sth@linux.ibm.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/s390/block/dasd_ioctl.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=dbf2ae34d2f1390a9fc1abf3dce7f809e022caae

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

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

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

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

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: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

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