# CVE-2026-74374: md/raid1,raid10: fix error-path detection with md_cloned_bio()

> A flaw in Linux kernel RAID1/10 error handling can cause deadlocks under memory pressure, leading to denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-96084, BELL-CVE-2026-74374, DEBIAN-CVE-2026-74374, GHSA-mr8x-hvpc-q7pw, UBUNTU-CVE-2026-74374

## What is CVE-2026-74374?

CVE-2026-74374 is a high-severity denial of service vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

md/raid1,raid10: fix error-path detection with md_cloned_bio()

Detect the error path using md_cloned_bio() instead of relying
on r1_bio in raid1 or r10_bio->read_slot in raid10, which may be
NULL or -1 after splitting and resubmitting a failed bio.

As a result, the error path may not be recognized and memory
allocations can incorrectly use GFP_NOIO instead of
(GFP_NOIO | __GFP_HIGH), which can lead to a deadlock under
memory pressure.

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


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

Apply the vendor's patch.

## Is CVE-2026-74374 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74374 is a high-severity denial of service vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74374 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-74374/ (Markdown: https://insights.sbomify.com/CVE-2026-74374/index.md)
```

## Sources

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

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