The flaw is a race condition between page migration and ext4 bitmap modification that can make the bitmap state momentarily inconsistent, causing the kernel to report e4b bitmap check failures and false‑positive corruption messages. The fix introduces a lock check so that the load_buddy routine takes the safe slow path when a folio is locked, eliminating the concurrency window and the associated error reports. Based on the description, the race can only be triggered under specific high‑load conditions, making direct exploitation unlikely.

Any installation of the Linux kernel that uses the ext4 filesystem and has not yet incorporated the described code changes is potentially affected. The CNA vendor list indicates "Linux:Linux", so all distributions shipping the upstream kernel before this patch could be vulnerable. No explicit kernel version range is supplied, so a check of the running kernel version against the patch set is required.

The CVSS score of 7.8 indicates a high severity when the race is triggered. The EPSS score of less than 1% and the absence from the CISA KEV catalog suggest a low likelihood of real‑world exploitation. The condition is extremely narrow and requires specific kernel and memory‑allocation timing, so the practical risk is moderate as the bug primarily results in error reporting rather than confirmed malicious exploitation. Based on the description, the likely attack vector is a local user triggering heavy filesystem activity to create the race, but the bug mainly causes error reports rather than destructive impact.