# CVE-2026-80679: s390/dasd: Fix potential NULL pointer dereference

> A NULL pointer dereference in the Linux kernel s390/dasd driver can cause a system crash, requiring a kernel patch.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** AZL-98156, BELL-CVE-2026-80679, DEBIAN-CVE-2026-80679, GHSA-68wp-mw9w-2vpr, UBUNTU-CVE-2026-80679

## What is CVE-2026-80679?

CVE-2026-80679 is a vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-80679?


## How do I fix CVE-2026-80679?

Apply the vendor's patch.

## Is CVE-2026-80679 being exploited?

There is no known exploitation of CVE-2026-80679 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80679 and fix it if it is affected.

What it is: CVE-2026-80679 is a vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80679 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80679/ (Markdown: https://insights.sbomify.com/CVE-2026-80679/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80679
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80679
- OSV: https://osv.dev/vulnerability/CVE-2026-80679

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80679/
Summaries are generated and may contain mistakes; the official description above is the record.