CVE-2026-74374 (GCVE-0-2026-74374)
Vulnerability from cvelistv5
Published
2026-08-15 05:58
Modified
2026-08-17 05:46
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 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.
Impacted products
Vendor Product Version
Linux Linux Version: 689389a06ce79fdced85b5115717f71c71e623e0
Version: 689389a06ce79fdced85b5115717f71c71e623e0
Create a notification for this product.
Show details on NVD website


{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/md/raid1.c",
            "drivers/md/raid10.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "20fb582c92fd64e5c8bd83c6176264b2794603b7",
              "status": "affected",
              "version": "689389a06ce79fdced85b5115717f71c71e623e0",
              "versionType": "git"
            },
            {
              "lessThan": "811545e0926d02a6a0b1a1258bb5544777c164d4",
              "status": "affected",
              "version": "689389a06ce79fdced85b5115717f71c71e623e0",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/md/raid1.c",
            "drivers/md/raid10.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "4.12"
            },
            {
              "lessThan": "4.12",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.1.*",
              "status": "unaffected",
              "version": "7.1.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1.5",
                  "versionStartIncluding": "4.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2",
                  "versionStartIncluding": "4.12",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmd/raid1,raid10: fix error-path detection with md_cloned_bio()\n\nDetect the error path using md_cloned_bio() instead of relying\non r1_bio in raid1 or r10_bio-\u003eread_slot in raid10, which may be\nNULL or -1 after splitting and resubmitting a failed bio.\n\nAs a result, the error path may not be recognized and memory\nallocations can incorrectly use GFP_NOIO instead of\n(GFP_NOIO | __GFP_HIGH), which can lead to a deadlock under\nmemory pressure."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.5,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:N - Linux file/NAS servers commonly export md RAID1/RAID10 volumes via nfsd, ksmbd, or iSCSI; remote client reads reach md_submit_bio()\u2192raid1/raid10_read_request(), and mirror read failures drive handle_read_error() on the blocked raid1d/raid10d thread without local shell access.\nAC:L - An attacker can reliably hit the bug by reading sectors on a degraded mirror that return errors (common on production arrays), issuing large reads that bio_submit_split_bioset() splits on the error-retry path, and concurrently applying memory pressure so GFP_NOIO bio_alloc_clone() blocks reclaim while raid1d/raid10d holds the array frozen.\nPR:N - Triggering the fault path requires only permission to read exported storage or files on an md-backed filesystem; no CAP_SYS_ADMIN, md ioctl, or init-namespace root is needed because read I/O and mirror error recovery run with no extra capability checks beyond normal block-device access.\nUI:N - No victim interaction is required; exploitation uses the attacker\u0027s own read I/O (or scripted NFS/SMB/iSCSI reads) together with memory pressure, without anyone mounting disks, acknowledging bad blocks, or performing other cooperative actions.\nS:U - The circular GFP_NOIO allocation wait while raid1d/raid10d is blocked in handle_read_error() freezes I/O within the same host kernel and md security domain; it does not cross VM, container, or IOMMU boundaries.\nC:N - This is a GFP-flag misclassification causing reclaim/I/O circular wait (deadlock), not memory corruption, out-of-bounds access, use-after-free, or other primitives that could disclose kernel or user data.\nI:N - The flaw does not enable arbitrary writes, code execution, or silent data modification; impact is limited to blocking forward progress in the RAID error-recovery path under memory pressure.\nA:H - Without __GFP_HIGH on the error path, bio_alloc_clone() can stall reclaim while raid1d/raid10d blocks with the array frozen, deadlocking all I/O to the md device and potentially hanging root/data volumes on enterprise RAID1/RAID10 servers."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-17T05:46:27.554Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/20fb582c92fd64e5c8bd83c6176264b2794603b7"
        },
        {
          "url": "https://git.kernel.org/stable/c/811545e0926d02a6a0b1a1258bb5544777c164d4"
        }
      ],
      "title": "md/raid1,raid10: fix error-path detection with md_cloned_bio()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-74374",
    "datePublished": "2026-08-15T05:58:53.659Z",
    "dateReserved": "2026-08-15T05:44:03.889Z",
    "dateUpdated": "2026-08-17T05:46:27.554Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…