---
id: CVE-2026-74374
title: |-
  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 …
summary: |-
  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 …
severity: high
cvss: 7.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 689389a06ce79fdced85b5115717f71c71e623e0 <
    029b363c9b690613141338436ac91366b1928af2
  - >-
    Linux >= 689389a06ce79fdced85b5115717f71c71e623e0 <
    20fb582c92fd64e5c8bd83c6176264b2794603b7
  - >-
    Linux >= 689389a06ce79fdced85b5115717f71c71e623e0 <
    811545e0926d02a6a0b1a1258bb5544777c164d4
  - Linux 4.12
published: '2026-08-15'
updated: '2026-10-15'
sourceUpdated: '2026-10-15T11:17:46.053'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-74374'
references:
  - url: 'https://git.kernel.org/stable/c/029b363c9b690613141338436ac91366b1928af2'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/20fb582c92fd64e5c8bd83c6176264b2794603b7'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/811545e0926d02a6a0b1a1258bb5544777c164d4'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
epss: 0.00488
epssPercentile: 0.4048
ingestedAt: '2026-10-15T11:00:41.675Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.