# CVE-2023-53722: md: raid1: fix potential OOB in raid1_remove_disk()

> An out-of-bounds memory access in the Linux kernel RAID1 driver allows local attackers to cause a denial of service or potentially execute code.

- **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:** 22 Oct 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2023-53722, DEBIAN-CVE-2023-53722, GHSA-564p-3xmp-v9fw, UBUNTU-CVE-2023-53722

## What is CVE-2023-53722?

CVE-2023-53722 is a memory corruption vulnerability in Linux, published on 22 Oct 2025. 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 potential OOB in raid1_remove_disk()

If rddev->raid_disk is greater than mddev->raid_disks, there will be
an out-of-bounds in raid1_remove_disk(). We have already found
similar reports as follows:

1) commit d17f744e883b ("md-raid10: fix KASAN warning")
2) commit 1ebc2cec0b7d ("dm raid: fix KASAN warning in raid5_remove_disk")

Fix this bug by checking whether the "number" variable is
valid.

## Which versions are affected by CVE-2023-53722?


## How do I fix CVE-2023-53722?

Apply the vendor's patch.

## Is CVE-2023-53722 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-53722 and fix it if it is affected.

What it is: CVE-2023-53722 is a memory corruption vulnerability in Linux, published on 22 Oct 2025. 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-2023-53722 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-2023-53722/ (Markdown: https://insights.sbomify.com/CVE-2023-53722/index.md)
```

## Sources

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

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