CVE-2026-80679

s390/dasd: Fix potential NULL pointer dereference

N/A

Published: August 28, 2026 at 06:52 AM UTC

Updated: August 28, 2026 at 08:32 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

N/A

Exploit prediction

EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: s390/dasd: Fix potential NULL pointer dereference 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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

5.3 ≤ v < 5.10.2655.3 ≤ v < 5.15.2165.3 ≤ v < 6.1.1835.3 ≤ v < 6.12.1035.3 ≤ v < 6.18.445.3 ≤ v < 6.6.1515.3 ≤ v < 7.1.85.3 ≤ v < 7.25.391dc4a197569230683ca8bad551e655a4bf14c30

Vendor states this is fixed in 3000367a512b1283ca52230bf21f8c91dfbec45b (fixed)

Vendor states this is fixed in 3453a993a3f14c1684560ecf26585046976f6ac6 (fixed)

Vendor states this is fixed in 86cdfd061509bcde84f3145f7221ba64e3e53b1f (fixed)

Vendor states this is fixed in 96b8e09b09539f252a5eeea6baebd93c2e3779bd (fixed)

Vendor states this is fixed in 9973026f572db6b67570cadc30942f3014e41079 (fixed)

Vendor states this is fixed in cdc7b73d0c5a9cd6360b4f8c36eae23b02097e4c (fixed)

Vendor states this is fixed in dbf2ae34d2f1390a9fc1abf3dce7f809e022caae (fixed)

Vendor states this is fixed in e156c70c505c6c9adce3b7be5a82025f00544709 (fixed)

Vendor states this is fixed in 5.10.265 (unaffected)

Vendor states this is fixed in 5.15.216 (unaffected)

Vendor states this is fixed in 5.3 (unaffected)

Vendor states this is fixed in 6.1.183 (unaffected)