CVE-2023-53620 Affecting kernel-debuginfo-common-aarch64 package, versions <0:6.1.34-56.100.amzn2023


Severity

Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.02% (5th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-AMZN2023-KERNELDEBUGINFOCOMMONAARCH64-13705648
  • published24 Oct 2025
  • disclosed7 Oct 2025

Introduced: 7 Oct 2025

NewCVE-2023-53620  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 kernel-debuginfo-common-aarch64 to version 0:6.1.34-56.100.amzn2023 or higher.
This issue was patched in ALAS2023-2023-228.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-debuginfo-common-aarch64 package and not the kernel-debuginfo-common-aarch64 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1