A race condition exists between the break_stripe_batch_list() routine and the raid5_make_request() routine in the Linux kernel’s md/raid5 driver. The two functions modify the R5_Overlap flag on a device’s dev[i] structure, one using a plain word write and the other an atomic bit operation. When the operations interleave, the kernel may fail to deliver a wake‑up to a waiting CPU, causing that processor to block indefinitely. Based on the description, the incorrect handling of the R5_Overlap flag could lead to data integrity issues if a RAID‑5 stripe list is mismanaged, though the vulnerability documentation does not explicitly confirm data corruption as a guaranteed outcome.

All Linux kernel builds that include the md/raid5 driver and have not yet incorporated the race‑condition fix are potentially affected. Version information is not provided in the CNA data, so any kernel that contains unpatched code remains at risk.

The CVSS score is 8.8 and the EPSS score is < 1%, and it is not listed in the CISA KEV catalog, indicating no widespread exploitation yet. A local attacker with kernel privileges could trigger the race by initiating write or read operations on a RAID‑5 device; the likely attack vector is local code that can run with elevated privileges. Based on the description, there is no known remote exploit path for this vulnerability. The impact is a denial of service through indefinite waits and potential data integrity loss if the overlap condition is incorrectly handled. Overall, the threat remains moderate to high for affected installations that run the affected kernel without a patch.