CVE-2024-38598 Details
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.
A soft lockup vulnerability has been identified in the Linux kernel's dm-raid10 module, specifically during the resynchronization process. This issue occurs when the bitmap size is smaller than the array size, leading to a mismatch that causes the CPU to become unresponsive. The problem is triggered by the 'lvextend' command combined with 'lvchange --syncaction', which initiates a resynchronization that can cause the CPU to be stuck for an extended period.
The vulnerability has been addressed in the official Linux kernel repository. Users can upgrade to the latest version to mitigate this issue.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Sep 10, 2024References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-667 | Improper Locking | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 4.19.291, < 4.19.316 >= 5.4.251, < 5.4.278 >= 5.10.188, < 5.10.219 >= 5.15.121, < 5.15.161 >= 6.1.39, < 6.1.93 >= 6.5, < 6.6.33 >= 6.7, < 6.8.12 >= 6.9, < 6.9.3 |
CPE
Remediation
| |
Change History
13 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 15, 2026 | CVE Modified | siemens-SADP |
| Oct 15, 2026 | CVE Modified | CVE |
| Oct 15, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | siemens-SADP |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| May 12, 2026 | CVE Modified | siemens-SADP |
| Nov 4, 2025 | CVE Modified | CVE |
| Nov 21, 2024 | CVE Modified | CVE |
| Aug 27, 2024 | Initial Analysis | [email protected] |
| Jul 15, 2024 | CVE Modified | kernel.org |
| Jun 27, 2024 | CVE Modified | kernel.org |
| Jun 19, 2024 | New CVE Received | kernel.org |