CVE-2023-53620
published 2025-10-07CVE-2023-53620: In the Linux kernel, the following vulnerability has been resolved: md: fix soft lockup in status_resync status_resync() will calculate 'curr_resync -…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.14%
4.0th percentile
In the Linux kernel, the following vulnerability has been resolved:
md: fix soft lockup in status_resync
status_resync() will calculate 'curr_resync - recovery_active' to show
user a progress bar like following:
[============>........] resync = 61.4%
'curr_resync' and 'recovery_active' is updated in md_do_sync(), and
status_resync() can read them concurrently, hence it's possible that
'curr_resync - recovery_active' can overflow to a huge number. In this
case status_resync() will be stuck in the loop to print a large amount
of '=', which will end up soft lockup.
Fix the problem by setting 'resync' to MD_RESYNC_ACTIVE in this case,
this way resync in progress will be reported to user.
Affected
11 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.37-1 (bookworm) | linux 6.1.37-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < b4acb6c3ede88d6b7d33742a09e63cfce5e7fb69 | b4acb6c3ede88d6b7d33742a09e63cfce5e7fb69 |
| linux | linux | >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 23309704e90859af2662bedc44101e6d1d2ece7e | 23309704e90859af2662bedc44101e6d1d2ece7e |
| linux | linux | >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 6efddf1e32e2a264694766ca485a4f5e04ee82a7 | 6efddf1e32e2a264694766ca485a4f5e04ee82a7 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 6.1.37-1 | 6.1.37-1 |
| linux | linux_kernel | >= 0 < 6.3.7-1 | 6.3.7-1 |
| linux | linux_kernel | >= 0 < 6.3.7-1 | 6.3.7-1 |
| linux | linux_kernel | >= 2.6.12.1 < 6.1.30 | 6.1.30 |
| linux | linux_kernel | >= 6.2 < 6.3.4 | 6.3.4 |
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_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.
VulDB
Linux Kernel up to 6.1.29/6.3.3 status_resync denial of service (Nessus ID 276910 / WID-SEC-2025-2229)
vuldb·2026-04-20·CVSS 5.5
CVE-2023-53620 [MEDIUM] Linux Kernel up to 6.1.29/6.3.3 status_resync denial of service (Nessus ID 276910 / WID-SEC-2025-2229)
A vulnerability classified as critical has been found in Linux Kernel up to 6.1.29/6.3.3. The affected element is the function status_resync. This manipulation causes denial of service.
This vulnerability is tracked as CVE-2023-53620. The attack is only possible within the local network. No exploit exists.
It is recommended to upgrade the affected component.
GHSA
GHSA-gjrx-w6pw-88ph: In the Linux kernel, the following vulnerability has been resolved:
md: fix soft lockup in status_resync
status_resync() will calculate 'curr_resync
ghsa_unreviewed·2025-10-07
CVE-2023-53620 [MEDIUM] CWE-667 GHSA-gjrx-w6pw-88ph: In the Linux kernel, the following vulnerability has been resolved:
md: fix soft lockup in status_resync
status_resync() will calculate 'curr_resync
In the Linux kernel, the following vulnerability has been resolved:
md: fix soft lockup in status_resync
status_resync() will calculate 'curr_resync - recovery_active' to show
user a progress bar like following:
[============>........] resync = 61.4%
'curr_resync' and 'recovery_active' is updated in md_do_sync(), and
status_resync() can read them concurrently, hence it's possible that
'curr_resync - recovery_active' can overflow to a huge number. In this
case status_resync() will be stuck in the loop to print a large amount
of '=', which will end up soft lockup.
Fix the problem by setting 'resync' to MD_RESYNC_ACTIVE in this case,
this way resync in progress will be reported to user.
OSV
CVE-2023-53620: In the Linux kernel, the following vulnerability has been resolved: md: fix soft lockup in status_resync status_resync() will calculate 'curr_resync -
osv·2025-10-07·CVSS 5.5
CVE-2023-53620 [MEDIUM] CVE-2023-53620: In the Linux kernel, the following vulnerability has been resolved: md: fix soft lockup in status_resync status_resync() will calculate 'curr_resync -
In the Linux kernel, the following vulnerability has been resolved: md: fix soft lockup in status_resync status_resync() will calculate 'curr_resync - recovery_active' to show user a progress bar like following: [============>........] resync = 61.4% 'curr_resync' and 'recovery_active' is updated in md_do_sync(), and status_resync() can read them concurrently, hence it's possible that 'curr_resync - recovery_active' can overflow to a huge number. In this case status_resync() will be stuck in the loop to print a large amount of '=', which will end up soft lockup. Fix the problem by setting 'resync' to MD_RESYNC_ACTIVE in this case, this way resync in progress will be reported to user.
Red Hat
kernel: md: fix soft lockup in status_resync
vendor_redhat·2025-10-07·CVSS 5.5
CVE-2023-53620 [MEDIUM] kernel: md: fix soft lockup in status_resync
kernel: md: fix soft lockup in status_resync
In the Linux kernel, the following vulnerability has been resolved:
md: fix soft lockup in status_resync
status_resync() will calculate 'curr_resync - recovery_active' to show
user a progress bar like following:
[============>........] resync = 61.4%
'curr_resync' and 'recovery_active' is updated in md_do_sync(), and
status_resync() can read them concurrently, hence it's possible that
'curr_resync - recovery_active' can overflow to a huge number. In this
case status_resync() will be stuck in the loop to print a large amount
of '=', which will end up soft lockup.
Fix the problem by setting 'resync' to MD_RESYNC_ACTIVE in this case,
this way resync in progress will be reported to user.
A logic flaw was found in the Linux kernel Multiple Device (
Debian
CVE-2023-53620: linux - In the Linux kernel, the following vulnerability has been resolved: md: fix sof...
vendor_debian·2023·CVSS 5.5
CVE-2023-53620 [MEDIUM] CVE-2023-53620: linux - In the Linux kernel, the following vulnerability has been resolved: md: fix sof...
In the Linux kernel, the following vulnerability has been resolved: md: fix soft lockup in status_resync status_resync() will calculate 'curr_resync - recovery_active' to show user a progress bar like following: [============>........] resync = 61.4% 'curr_resync' and 'recovery_active' is updated in md_do_sync(), and status_resync() can read them concurrently, hence it's possible that 'curr_resync - recovery_active' can overflow to a huge number. In this case status_resync() will be stuck in the loop to print a large amount of '=', which will end up soft lockup. Fix the problem by setting 'resync' to MD_RESYNC_ACTIVE in this case, this way resync in progress will be reported to user.
Scope: local
bookworm: resolved (fixed in 6.1.37-1)
bullseye: open
forky: resolved (fixed in 6.3.7-1)
sid:
No detection rules found.
No public exploits indexed.
2025-10-07
Published