{"api_version":"1","generated_at":"2026-08-15T08:44:18+00:00","cve":"CVE-2026-74372","urls":{"html":"https://cve.report/CVE-2026-74372","api":"https://cve.report/api/cve/CVE-2026-74372.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-74372","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-74372"},"summary":{"title":"raid1: fix nr_pending leak in REQ_ATOMIC bad-block error path","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nraid1: fix nr_pending leak in REQ_ATOMIC bad-block error path\n\nIn raid1_write_request(), each per-mirror loop iteration begins by\nincrementing rdev->nr_pending. If a REQ_ATOMIC write encounters a\nbadblock within the requested range, the code jumps to err_handle\nwithout dropping the reference taken for the current mirror.\n\nerr_handle's cleanup loop will only decrements for k < i and\nr1_bio->bios[k] is non-NULL. The current slot is therefore skipped,\nleaving its nr_pending reference leaked permanently. The reference\nprevents the rdev from ever being removed, since raid1_remove_conf()\nrefuses to remove an rdev with nr_pending > 0.\n\nFix this by calling rdev_dec_pending() before jumping to err_handle.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-15 06:22:38","updated_at":"2026-08-15 06:22:38"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/909d9dc3b5730c8ed7b764c68bc788342df2a07b","name":"https://git.kernel.org/stable/c/909d9dc3b5730c8ed7b764c68bc788342df2a07b","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/731485617bf862f1289c3f40ed1f800d0475826f","name":"https://git.kernel.org/stable/c/731485617bf862f1289c3f40ed1f800d0475826f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/5ac9e793ba2583d72740d929e7858a6c82e22ed5","name":"https://git.kernel.org/stable/c/5ac9e793ba2583d72740d929e7858a6c82e22ed5","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-74372","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74372","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f2a38abf5f1c5aeb3be8e9f4d3d815c867fff7ca 5ac9e793ba2583d72740d929e7858a6c82e22ed5 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f2a38abf5f1c5aeb3be8e9f4d3d815c867fff7ca 731485617bf862f1289c3f40ed1f800d0475826f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f2a38abf5f1c5aeb3be8e9f4d3d815c867fff7ca 909d9dc3b5730c8ed7b764c68bc788342df2a07b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.13","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.13 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.40 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.5 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/md/raid1.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"5ac9e793ba2583d72740d929e7858a6c82e22ed5","status":"affected","version":"f2a38abf5f1c5aeb3be8e9f4d3d815c867fff7ca","versionType":"git"},{"lessThan":"731485617bf862f1289c3f40ed1f800d0475826f","status":"affected","version":"f2a38abf5f1c5aeb3be8e9f4d3d815c867fff7ca","versionType":"git"},{"lessThan":"909d9dc3b5730c8ed7b764c68bc788342df2a07b","status":"affected","version":"f2a38abf5f1c5aeb3be8e9f4d3d815c867fff7ca","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/md/raid1.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.13"},{"lessThan":"6.13","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.40","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.40","versionStartIncluding":"6.13","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.5","versionStartIncluding":"6.13","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2-rc1","versionStartIncluding":"6.13","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nraid1: fix nr_pending leak in REQ_ATOMIC bad-block error path\n\nIn raid1_write_request(), each per-mirror loop iteration begins by\nincrementing rdev->nr_pending. If a REQ_ATOMIC write encounters a\nbadblock within the requested range, the code jumps to err_handle\nwithout dropping the reference taken for the current mirror.\n\nerr_handle's cleanup loop will only decrements for k < i and\nr1_bio->bios[k] is non-NULL. The current slot is therefore skipped,\nleaving its nr_pending reference leaked permanently. The reference\nprevents the rdev from ever being removed, since raid1_remove_conf()\nrefuses to remove an rdev with nr_pending > 0.\n\nFix this by calling rdev_dec_pending() before jumping to err_handle."}],"providerMetadata":{"dateUpdated":"2026-08-15T05:58:52.306Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/5ac9e793ba2583d72740d929e7858a6c82e22ed5"},{"url":"https://git.kernel.org/stable/c/731485617bf862f1289c3f40ed1f800d0475826f"},{"url":"https://git.kernel.org/stable/c/909d9dc3b5730c8ed7b764c68bc788342df2a07b"}],"title":"raid1: fix nr_pending leak in REQ_ATOMIC bad-block error path","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-74372","datePublished":"2026-08-15T05:58:52.306Z","dateReserved":"2026-08-15T05:44:03.889Z","dateUpdated":"2026-08-15T05:58:52.306Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-15 06:22:38","lastModifiedDate":"2026-08-15 06:22:38","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"74372","Ordinal":"1","Title":"raid1: fix nr_pending leak in REQ_ATOMIC bad-block error path","CVE":"CVE-2026-74372","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"74372","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nraid1: fix nr_pending leak in REQ_ATOMIC bad-block error path\n\nIn raid1_write_request(), each per-mirror loop iteration begins by\nincrementing rdev->nr_pending. If a REQ_ATOMIC write encounters a\nbadblock within the requested range, the code jumps to err_handle\nwithout dropping the reference taken for the current mirror.\n\nerr_handle's cleanup loop will only decrements for k < i and\nr1_bio->bios[k] is non-NULL. The current slot is therefore skipped,\nleaving its nr_pending reference leaked permanently. The reference\nprevents the rdev from ever being removed, since raid1_remove_conf()\nrefuses to remove an rdev with nr_pending > 0.\n\nFix this by calling rdev_dec_pending() before jumping to err_handle.","Type":"Description","Title":"raid1: fix nr_pending leak in REQ_ATOMIC bad-block error path"}]}}}