# CVE-2024-45026: s390/dasd: fix error recovery leading to data corruption on ESE devices

> A flaw in the s390/dasd driver causes data corruption on ESE devices during specific error recovery scenarios, requiring a kernel patch.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2024
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-49187, AZL-49266, BELL-CVE-2024-45026, DEBIAN-CVE-2024-45026, GHSA-66cw-5j4x-3r2w, ROOT-OS-DEBIAN-11-CVE-2024-45026, UBUNTU-CVE-2024-45026

## What is CVE-2024-45026?

CVE-2024-45026 is a high-severity vulnerability in Linux kernel, published on 11 Sep 2024. 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 error recovery leading to data corruption on ESE devices

Extent Space Efficient (ESE) or thin provisioned volumes need to be
formatted on demand during usual IO processing.

The dasd_ese_needs_format function checks for error codes that signal
the non existence of a proper track format.

The check for incorrect length is to imprecise since other error cases
leading to transport of insufficient data also have this flag set.
This might lead to data corruption in certain error cases for example
during a storage server warmstart.

Fix by removing the check for incorrect length and replacing by
explicitly checking for invalid track format in transport mode.

Also remove the check for file protected since this is not a valid
ESE handling case.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2024-45026?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-45026?

Apply the vendor's patch.

## Is CVE-2024-45026 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-45026 and fix it if it is affected.

What it is: CVE-2024-45026 is a high-severity vulnerability in Linux kernel, published on 11 Sep 2024. 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-2024-45026 in the wild and no public exploit code.

Affected product: Linux kernel. 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-2024-45026/ (Markdown: https://insights.sbomify.com/CVE-2024-45026/index.md)
```

## Sources

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

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