{"id":"CVE-2026-74374","state":"PUBLISHED","title":"md/raid1,raid10: fix error-path detection with md_cloned_bio()","description":"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->read_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.","publishedAt":"2026-08-15T05:58:53.659Z","updatedAt":"2026-10-21T12:45:31.666Z","severity":{"score":7.5,"label":"High","version":"3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","source":"Linux"},"assigner":"Linux","products":["Linux Linux"],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"689389a06ce79fdced85b5115717f71c71e623e0","status":"affected","lessThan":"80eaeae0e4b1ed2418fd2b9088238651fb51df69","versionType":"git"},{"version":"689389a06ce79fdced85b5115717f71c71e623e0","status":"affected","lessThan":"8719aa0f57955fd641f952d16e02fc6b4934c6e3","versionType":"git"},{"version":"689389a06ce79fdced85b5115717f71c71e623e0","status":"affected","lessThan":"029b363c9b690613141338436ac91366b1928af2","versionType":"git"},{"version":"689389a06ce79fdced85b5115717f71c71e623e0","status":"affected","lessThan":"20fb582c92fd64e5c8bd83c6176264b2794603b7","versionType":"git"},{"version":"689389a06ce79fdced85b5115717f71c71e623e0","status":"affected","lessThan":"811545e0926d02a6a0b1a1258bb5544777c164d4","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/md/raid1.c","drivers/md/raid10.c"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"4.12","status":"affected"},{"version":"0","status":"unaffected","lessThan":"4.12","versionType":"semver"},{"version":"6.6.160","status":"unaffected","lessThanOrEqual":"6.6.*","versionType":"semver"},{"version":"6.12.114","status":"unaffected","lessThanOrEqual":"6.12.*","versionType":"semver"},{"version":"6.18.57","status":"unaffected","lessThanOrEqual":"6.18.*","versionType":"semver"},{"version":"7.1.5","status":"unaffected","lessThanOrEqual":"7.1.*","versionType":"semver"},{"version":"7.2","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/md/raid1.c","drivers/md/raid10.c"]}],"references":["https://git.kernel.org/stable/c/80eaeae0e4b1ed2418fd2b9088238651fb51df69","https://git.kernel.org/stable/c/8719aa0f57955fd641f952d16e02fc6b4934c6e3","https://git.kernel.org/stable/c/029b363c9b690613141338436ac91366b1928af2","https://git.kernel.org/stable/c/20fb582c92fd64e5c8bd83c6176264b2794603b7","https://git.kernel.org/stable/c/811545e0926d02a6a0b1a1258bb5544777c164d4"],"weaknesses":[],"ingestedAt":"2026-10-29T20:12:58.252Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2026/74xxx/CVE-2026-74374.json","commit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-74374","state":"PUBLISHED","datePublished":"2026-08-15T05:58:53.659Z","dateUpdated":"2026-10-21T12:45:31.666Z","assignerShortName":"Linux","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateReserved":"2026-08-15T05:44:03.889Z"},"containers":{"cna":{"title":"md/raid1,raid10: fix error-path detection with md_cloned_bio()","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->read_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."}],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"689389a06ce79fdced85b5115717f71c71e623e0","status":"affected","lessThan":"80eaeae0e4b1ed2418fd2b9088238651fb51df69","versionType":"git"},{"version":"689389a06ce79fdced85b5115717f71c71e623e0","status":"affected","lessThan":"8719aa0f57955fd641f952d16e02fc6b4934c6e3","versionType":"git"},{"version":"689389a06ce79fdced85b5115717f71c71e623e0","status":"affected","lessThan":"029b363c9b690613141338436ac91366b1928af2","versionType":"git"},{"version":"689389a06ce79fdced85b5115717f71c71e623e0","status":"affected","lessThan":"20fb582c92fd64e5c8bd83c6176264b2794603b7","versionType":"git"},{"version":"689389a06ce79fdced85b5115717f71c71e623e0","status":"affected","lessThan":"811545e0926d02a6a0b1a1258bb5544777c164d4","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/md/raid1.c","drivers/md/raid10.c"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"4.12","status":"affected"},{"version":"0","status":"unaffected","lessThan":"4.12","versionType":"semver"},{"version":"6.6.160","status":"unaffected","lessThanOrEqual":"6.6.*","versionType":"semver"},{"version":"6.12.114","status":"unaffected","lessThanOrEqual":"6.12.*","versionType":"semver"},{"version":"6.18.57","status":"unaffected","lessThanOrEqual":"6.18.*","versionType":"semver"},{"version":"7.1.5","status":"unaffected","lessThanOrEqual":"7.1.*","versionType":"semver"},{"version":"7.2","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/md/raid1.c","drivers/md/raid10.c"]}],"references":[{"url":"https://git.kernel.org/stable/c/80eaeae0e4b1ed2418fd2b9088238651fb51df69"},{"url":"https://git.kernel.org/stable/c/8719aa0f57955fd641f952d16e02fc6b4934c6e3"},{"url":"https://git.kernel.org/stable/c/029b363c9b690613141338436ac91366b1928af2"},{"url":"https://git.kernel.org/stable/c/20fb582c92fd64e5c8bd83c6176264b2794603b7"},{"url":"https://git.kernel.org/stable/c/811545e0926d02a6a0b1a1258bb5544777c164d4"}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","baseScore":7.5,"baseSeverity":"HIGH"},"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()→raid1/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's 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":{"shortName":"Linux","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateUpdated":"2026-10-21T12:45:31.666Z"},"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.12","versionEndExcluding":"6.6.160"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.12","versionEndExcluding":"6.12.114"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.12","versionEndExcluding":"6.18.57"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.12","versionEndExcluding":"7.1.5"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.12","versionEndExcluding":"7.2"}]}]}],"x_generator":{"engine":"bippy-1.2.0"}},"adp":[{"title":"CISA ADP Vulnrichment","metrics":[{"other":{"type":"ssvc","content":{"id":"CVE-2026-74374","role":"CISA Coordinator","options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"partial"}],"version":"2.0.3","timestamp":"2026-10-16T18:54:43.023630Z"}}}],"providerMetadata":{"shortName":"CISA-ADP","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","dateUpdated":"2026-10-16T18:55:36.037Z"}}]}}}