# CVE-2025-22125: md/raid1,raid10: don't ignore IO flags

> Attackers can degrade RAID write performance and cause priority reversals by exploiting ignored IO flags when blk-wbt is enabled.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 16 Apr 2025
- **Updated:** 11 May 2026
- **Also known as:** AZL-62504, AZL-69611, BELL-CVE-2025-22125, DEBIAN-CVE-2025-22125, GHSA-3wr8-w2fq-6q7v, ROOT-OS-DEBIAN-11-CVE-2025-22125, ROOT-OS-DEBIAN-12-CVE-2025-22125, ROOT-OS-DEBIAN-13-CVE-2025-22125, ROOT-OS-UBUNTU-2204-CVE-2025-22125, ROOT-OS-UBUNTU-2404-CVE-2025-22125, UBUNTU-CVE-2025-22125

## What is CVE-2025-22125?

CVE-2025-22125 is a medium-severity denial of service vulnerability in Linux kernel, published on 16 Apr 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,raid10: don't ignore IO flags

If blk-wbt is enabled by default, it's found that raid write performance
is quite bad because all IO are throttled by wbt of underlying disks,
due to flag REQ_IDLE is ignored. And turns out this behaviour exist since
blk-wbt is introduced.

Other than REQ_IDLE, other flags should not be ignored as well, for
example REQ_META can be set for filesystems, clearing it can cause priority
reverse problems; And REQ_NOWAIT should not be cleared as well, because
io will wait instead of failing directly in underlying disks.

Fix those problems by keep IO flags from master bio.

Fises: f51d46d0e7cb ("md: add support for REQ_NOWAIT")

## Which versions are affected by CVE-2025-22125?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-22125?

Apply the vendor's patch.

## Is CVE-2025-22125 being exploited?

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

What it is: CVE-2025-22125 is a medium-severity denial of service vulnerability in Linux kernel, published on 16 Apr 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-2025-22125 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-2025-22125/ (Markdown: https://insights.sbomify.com/CVE-2025-22125/index.md)
```

## Sources

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

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