# CVE-2024-45023: md/raid1: Fix data corruption for degraded array with slow disk

> Attackers can read unrecovered data from degraded RAID1 arrays with slow disks, leading to data corruption and integrity issues.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/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:** BELL-CVE-2024-45023, DEBIAN-CVE-2024-45023, GHSA-p5xc-g9x9-74jh, UBUNTU-CVE-2024-45023

## What is CVE-2024-45023?

CVE-2024-45023 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:

md/raid1: Fix data corruption for degraded array with slow disk

read_balance() will avoid reading from slow disks as much as possible,
however, if valid data only lands in slow disks, and a new normal disk
is still in recovery, unrecovered data can be read:

raid1_read_request
 read_balance
  raid1_should_read_first
  -> return false
  choose_best_rdev
  -> normal disk is not recovered, return -1
  choose_bb_rdev
  -> missing the checking of recovery, return the normal disk
 -> read unrecovered data

Root cause is that the checking of recovery is missing in
choose_bb_rdev(). Hence add such checking to fix the problem.

Also fix similar problem in choose_slow_rdev().

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

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-45023 being exploited?

There is no known exploitation of CVE-2024-45023 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-45023 and fix it if it is affected.

What it is: CVE-2024-45023 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-45023 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-45023/ (Markdown: https://insights.sbomify.com/CVE-2024-45023/index.md)
```

## Sources

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

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