CVE-2026-72420: md/raid5: avoid R5_Overlap races while breaking stripe batches
In the Linux kernel, the following vulnerability has been resolved:
md/raid5: avoid R5Overlap races while breaking stripe batches
KCSAN report a race in breakstripebatchlist() vs. raid5makerequest() on sh->dev[i].flags (plain word write vs. atomic bit op)..
and .. one possible scenario is:
CPU1 CPU2 breakstripebatchlist(sh1) -> handle sh2 -> lock(sh2) -> sh2->batchhead = NULL -> unlock(sh2) -> testandclearbit(R5Overlap, sh2->dev[i].flags) -> wakeupbit(sh2->dev[i].flags) raid5makerequest() -> addallstripebios(sh2) -> lock(sh2) -> stripebiooverlaps(sh2) returns true batchhead is NULL, so new bio overlap exist bio on sh2 -> true -> setbit(R5Overlap, sh2->dev[i].flags) -> unlock(sh2) -> waitonbit(sh2->dev[i].flags) -> sh2->dev[i].flags = sh1->dev[i].flags & ~R5Overlap
No waitupbit(), CPU2 could be waitonbit() forever...
Fix by : - Expand the protect zone. - Use batchhead's device flag's snaphot when no held headsh->stripelock. - Move sh/headsh->batchhead = NULL to the end of protected zone , and , any concurrent addallstripebios() grabs sh->stripelock now either: - see batchhead != null, and , is rejected by stripebiooverlaps() under the lock (no R5Overlap wait ) , or , - sees batchhead == NULL, only after dev[i].flags has already been set and the prior R5Overlap waiters worken.
KCSAN report: ================================================ BUG: KCSAN: data-race in breakstripebatchlist / raid5makerequest
write (marked) to 0xffff8e89c8117548 of 8 bytes by task 4042 on cpu 0: raid5makerequest+0xea0/0x2930 mdhandlerequest+0x4a2/0xa40 mdsubmitbio+0x109/0x1a0 submitbio+0x2ec/0x390 submitbionoacctnocheck+0x457/0x710 submitbionoacct+0x2a7/0xc20 submitbio+0x56/0x250 blkdevdirectIO+0x54c/0xda0 blkdevwriteiter+0x38f/0x570 aiowrite+0x22b/0x490 iosubmitone+0xa51/0xf70 x64sysiosubmit+0xf7/0x220 x64syscall+0x1907/0x1c60 dosyscall64+0x130/0x570 entrySYSCALL64afterhwframe+0x76/0x7e
read to 0xffff8e89c8117548 of 8 bytes by task 4010 on cpu 5: breakstripebatchlist+0x249/0x480 handlestripecleanevent+0x720/0x9b0 handlestripe+0x32fb/0x4500 handleactivestripes.isra.0+0x6e0/0xa50 raid5d+0x7e0/0xba0 mdthread+0x15a/0x2d0 kthread+0x1e3/0x220 retfromfork+0x37a/0x410 retfromforkasm+0x1a/0x30
value changed: 0x0000000000000019 -> 0x0000000000000099 --> R5Overlap
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 6.8.0-147.147 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 6.8.0-1067.70 - Upgrade
Upgrade
ubuntu/linux-aws-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1014.14~24.04.1 - Upgrade
Upgrade
ubuntu/linux-azureto a version that resolves this vulnerability.Fixed in 6.8.0-1071.79 - Upgrade
Upgrade
ubuntu/linux-azure-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17~24.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-fdeto a version that resolves this vulnerability.Fixed in 6.8.0-1069.76 - Upgrade
Upgrade
ubuntu/linux-azure-fde-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1016.16~24.04.1 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 6.8.0-1071.79 - Upgrade
Upgrade
ubuntu/linux-gcp-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1014.14~24.04.1 - Upgrade
Upgrade
ubuntu/linux-gketo a version that resolves this vulnerability.Fixed in 6.8.0-1066.74 - Upgrade
Upgrade
ubuntu/linux-gkeopto a version that resolves this vulnerability.Fixed in 6.8.0-1052.56 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-38.38~24.04.4 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 6.8.0-1067.68 - Upgrade
Upgrade
ubuntu/linux-lowlatencyto a version that resolves this vulnerability.Fixed in 6.8.0-147.147.1 - Upgrade
Upgrade
ubuntu/linux-nvidia-tegrato a version that resolves this vulnerability.Fixed in 6.8.0-1036.39 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 6.8.0-1064.67 - Upgrade
Upgrade
ubuntu/linux-oracle-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1013.13~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-38.38.1~24.04.1 - Upgrade
Upgrade
ubuntu/linux-bluefieldto a version that resolves this vulnerability.Fixed in 6.8.0-1033.38 - Upgrade
Upgrade
ubuntu/linux-realtimeto a version that resolves this vulnerability.Fixed in 6.8.1-1062.63 - Upgrade
Upgrade
ubuntu/linux-aws-fipsto a version that resolves this vulnerability.Fixed in 6.8.0-1067.70+fips1 - Upgrade
Upgrade
ubuntu/linux-azure-fipsto a version that resolves this vulnerability.Fixed in 6.8.0-1071.79+fips1 - Upgrade
Upgrade
ubuntu/linux-fipsto a version that resolves this vulnerability.Fixed in 6.8.0-147.147+fips1 - Upgrade
Upgrade
ubuntu/linux-gcp-fipsto a version that resolves this vulnerability.Fixed in 6.8.0-1071.79+fips1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-38.38 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1014.14 - Upgrade
Upgrade
ubuntu/linux-azureto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-azure-fdeto a version that resolves this vulnerability.Fixed in 7.0.0-1016.16 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1014.14 - Upgrade
Upgrade
ubuntu/linux-gketo a version that resolves this vulnerability.Fixed in 7.0.0-1008.9 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1015.15 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1015.15 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1013.13 - Upgrade
Upgrade
ubuntu/linux-realtimeto a version that resolves this vulnerability.Fixed in 7.0.0-38.38.1 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-38.38.1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.100-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.1.5-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.14-1 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.191 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.160 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.97 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.40 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.1.5 - Compensating control
In md/raid5, expand the protected zone: move `sh/head_sh->batch_head = NULL` to the end of the protected zone, and use `batch_head` device-flag snapshots when `head_sh->stripe_lock` is not held, so concurrent `add_all_stripe_bios()` operations either reject overlaps while holding `stripe_lock` or observe `batch_head == NULL` only after `dev[i].flags` is set and prior `R5_Overlap` waiters are awakened.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-72420?
The severity of CVE-2026-72420 is rated at 34.
How do I fix CVE-2026-72420?
To fix CVE-2026-72420, update your Linux kernel to the latest version where the vulnerability has been resolved.
What systems are affected by CVE-2026-72420?
CVE-2026-72420 affects the Linux kernel specifically relating to md/raid5 implementations.
What type of vulnerability is CVE-2026-72420?
CVE-2026-72420 is a race condition vulnerability that can occur during stripe batch processing in RAID 5.
Is CVE-2026-72420 currently under active exploitation?
As of the last update, there is no indication that CVE-2026-72420 is being actively exploited in the wild.