CVE-2024-26756
published 2024-04-03CVE-2024-26756: In the Linux kernel, the following vulnerability has been resolved: md: Don't register sync_thread for reshape directly Currently, if reshape is interrupted…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.21%
11.1th percentile
In the Linux kernel, the following vulnerability has been resolved:
md: Don't register sync_thread for reshape directly
Currently, if reshape is interrupted, then reassemble the array will
register sync_thread directly from pers->run(), in this case
'MD_RECOVERY_RUNNING' is set directly, however, there is no guarantee
that md_do_sync() will be executed, hence stop_sync_thread() will hang
because 'MD_RECOVERY_RUNNING' can't be cleared.
Last patch make sure that md_do_sync() will set MD_RECOVERY_DONE,
however, following hang can still be triggered by dm-raid test
shell/lvconvert-raid-reshape.sh occasionally:
[root@fedora ~]# cat /proc/1982/stack
[] stop_sync_thread+0x1ab/0x270 [md_mod]
[] md_frozen_sync_thread+0x5c/0xa0 [md_mod]
[] raid_presuspend+0x1e/0x70 [dm_raid]
[] dm_table_presuspend_targets+0x40/0xb0 [dm_mod]
[] __dm_destroy+0x2a5/0x310 [dm_mod]
[] dm_destroy+0x16/0x30 [dm_mod]
[] dev_remove+0x165/0x290 [dm_mod]
[] ctl_ioctl+0x4bb/0x7b0 [dm_mod]
[] dm_ctl_ioctl+0x11/0x20 [dm_mod]
[] vfs_ioctl+0x21/0x60
[] __x64_sys_ioctl+0xb9/0xe0
[] do_syscall_64+0xc6/0x230
[] entry_SYSCALL_64_after_hwframe+0x6c/0x74
Meanwhile mddev->recovery is:
MD_RECOVERY_RUNNING |
MD_RECOVERY_INTR |
MD_RECOVERY_RESHAPE |
MD_RECOVERY_FROZEN
Fix this problem by remove the code to register sync_thread directly
from raid10 and raid5. And let md_check_recovery() to register
sync_thread.
Affected
21 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.7.7-1 (forky) | linux 6.7.7-1 (forky) |
| linux | linux | — | — |
| linux | linux | >= f67055780caac6a99f43834795c43acf99eba6a6 < 13b520fb62b772e408f9b79c5fe18ad414e90417 | 13b520fb62b772e408f9b79c5fe18ad414e90417 |
| linux | linux | >= f67055780caac6a99f43834795c43acf99eba6a6 < ad39c08186f8a0f221337985036ba86731d6aafe | ad39c08186f8a0f221337985036ba86731d6aafe |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 6.7.7-1 | 6.7.7-1 |
| linux | linux_kernel | >= 0 < 6.7.7-1 | 6.7.7-1 |
| linux | linux_kernel | >= 2.6.17 < 6.7.7 | 6.7.7 |
| msrc | azl3_kernel_6.6.104.2-4_on_azure_linux_3.0 | — | — |
| msrc | azl3_kernel_6.6.112.1-2_on_azure_linux_3.0 | — | — |
| msrc | azl3_kernel_6.6.117.1-1_on_azure_linux_3.0 | — | — |
| msrc | azl3_kernel_6.6.119.3-1_on_azure_linux_3.0 | — | — |
| msrc | azl3_kernel_6.6.119.3-3_on_azure_linux_3.0 | — | — |
| msrc | azl3_kernel_6.6.121.1-1_on_azure_linux_3.0 | — | — |
| msrc | azl3_kernel_6.6.126.1-1_on_azure_linux_3.0 | — | — |
| msrc | azl3_kernel_6.6.130.1-3_on_azure_linux_3.0 | — | — |
| msrc | azl3_kernel_6.6.96.2-1_on_azure_linux_3.0 | — | — |
| msrc | azl3_kernel_6.6.96.2-2_on_azure_linux_3.0 | — | — |
| msrc | cbl2_kernel_5.15.186.1-1_on_cbl_mariner_2.0 | — | — |
| msrc | cbl2_kernel_5.15.200.1-1_on_cbl_mariner_2.0 | — | — |
| msrc | cbl2_kernel_5.15.202.1-1_on_cbl_mariner_2.0 | — | — |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_msrc5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Microsoft
md: Don't register sync_thread for reshape directly
vendor_msrc·2024-04-09·CVSS 5.5
CVE-2024-26756 [MEDIUM] CWE-459 md: Don't register sync_thread for reshape directly
md: Don't register sync_thread for reshape directly
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If impact to additional products is identified, we will update the CVE to reflect this.
Mariner: Mariner
Linux: Linux
Customer Action Required: Yes
Red Hat
kernel: md: Don't register sync_thread for reshape directly
vendor_redhat·2024-04-03·CVSS 5.5
CVE-2024-26756 [MEDIUM] CWE-20 kernel: md: Don't register sync_thread for reshape directly
kernel: md: Don't register sync_thread for reshape directly
In the Linux kernel, the following vulnerability has been resolved:
md: Don't register sync_thread for reshape directly
Currently, if reshape is interrupted, then reassemble the array will
register sync_thread directly from pers->run(), in this case
'MD_RECOVERY_RUNNING' is set directly, however, there is no guarantee
that md_do_sync() will be executed, hence stop_sync_thread() will hang
because 'MD_RECOVERY_RUNNING' can't be cleared.
Last patch make sure that md_do_sync() will set MD_RECOVERY_DONE,
however, following hang can still be triggered by dm-raid test
shell/lvconvert-raid-reshape.sh occasionally:
[root@fedora ~]# cat /proc/1982/stack
[] stop_sync_thread+0x1ab/0x270 [md_mod]
[] md_frozen_sync_thread+0x5c/0xa0 [md_mod]
[]
Debian
CVE-2024-26756: linux - In the Linux kernel, the following vulnerability has been resolved: md: Don't r...
vendor_debian·2024·CVSS 5.5
CVE-2024-26756 [MEDIUM] CVE-2024-26756: linux - In the Linux kernel, the following vulnerability has been resolved: md: Don't r...
In the Linux kernel, the following vulnerability has been resolved: md: Don't register sync_thread for reshape directly Currently, if reshape is interrupted, then reassemble the array will register sync_thread directly from pers->run(), in this case 'MD_RECOVERY_RUNNING' is set directly, however, there is no guarantee that md_do_sync() will be executed, hence stop_sync_thread() will hang because 'MD_RECOVERY_RUNNING' can't be cleared. Last patch make sure that md_do_sync() will set MD_RECOVERY_DONE, however, following hang can still be triggered by dm-raid test shell/lvconvert-raid-reshape.sh occasionally: [root@fedora ~]# cat /proc/1982/stack [] stop_sync_thread+0x1ab/0x270 [md_mod] [] md_frozen_sync_thread+0x5c/0xa0 [md_mod] [] raid_presuspend+0x1e/0x70 [dm_raid] [] dm_table_presuspend_t
OSV
CVE-2024-26756: In the Linux kernel, the following vulnerability has been resolved: md: Don't register sync_thread for reshape directly Currently, if reshape is inter
osv·2024-04-03·CVSS 5.5
CVE-2024-26756 [MEDIUM] CVE-2024-26756: In the Linux kernel, the following vulnerability has been resolved: md: Don't register sync_thread for reshape directly Currently, if reshape is inter
In the Linux kernel, the following vulnerability has been resolved: md: Don't register sync_thread for reshape directly Currently, if reshape is interrupted, then reassemble the array will register sync_thread directly from pers->run(), in this case 'MD_RECOVERY_RUNNING' is set directly, however, there is no guarantee that md_do_sync() will be executed, hence stop_sync_thread() will hang because 'MD_RECOVERY_RUNNING' can't be cleared. Last patch make sure that md_do_sync() will set MD_RECOVERY_DONE, however, following hang can still be triggered by dm-raid test shell/lvconvert-raid-reshape.sh occasionally: [root@fedora ~]# cat /proc/1982/stack [] stop_sync_thread+0x1ab/0x270 [md_mod] [] md_frozen_sync_thread+0x5c/0xa0 [md_mod] [] raid_presuspend+0x1e/0x70 [dm_raid] [] dm_table_presuspend_t
GHSA
GHSA-85g7-5359-r834: In the Linux kernel, the following vulnerability has been resolved:
md: Don't register sync_thread for reshape directly
Currently, if reshape is int
ghsa_unreviewed·2024-04-03
CVE-2024-26756 [MEDIUM] CWE-459 GHSA-85g7-5359-r834: In the Linux kernel, the following vulnerability has been resolved:
md: Don't register sync_thread for reshape directly
Currently, if reshape is int
In the Linux kernel, the following vulnerability has been resolved:
md: Don't register sync_thread for reshape directly
Currently, if reshape is interrupted, then reassemble the array will
register sync_thread directly from pers->run(), in this case
'MD_RECOVERY_RUNNING' is set directly, however, there is no guarantee
that md_do_sync() will be executed, hence stop_sync_thread() will hang
because 'MD_RECOVERY_RUNNING' can't be cleared.
Last patch make sure that md_do_sync() will set MD_RECOVERY_DONE,
however, following hang can still be triggered by dm-raid test
shell/lvconvert-raid-reshape.sh occasionally:
[root@fedora ~]# cat /proc/1982/stack
[] stop_sync_thread+0x1ab/0x270 [md_mod]
[] md_frozen_sync_thread+0x5c/0xa0 [md_mod]
[] raid_presuspend+0x1e/0x70 [dm_raid]
[] dm_table_presuspe
No detection rules found.
No public exploits indexed.
2024-04-03
Published