LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53620: 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can cause a system soft lockup while reporting software RAID resync progress. It is an availability risk, not a disclosed data theft or privilege escalation issue. Exposure appears limited to systems using the kernel md subsystem during resync or recovery status reporting.

Executive priority

Treat as a targeted reliability issue for Linux systems using software RAID. It should be remediated through normal kernel patching, with higher urgency for storage-heavy servers where a soft lockup could disrupt service availability.

Technical view

In md status_resync(), concurrent reads of curr_resync and recovery_active can make curr_resync - recovery_active overflow. The resulting huge resync value can trap status output generation in a long loop printing progress characters, leading to a soft lockup. The kernel fix clamps this case to MD_RESYNC_ACTIVE.

Likely exposure

Linux systems using md software RAID are the relevant exposure, especially when arrays are resyncing or recovering. The source lists Linux kernel versions and stable commits, but distro-specific affected package ranges are not provided.

Exploitation context

The bundle does not show active exploitation, public weaponization, KEV listing, CVSS, or CWE classification. Evidence supports a kernel availability bug reachable through md resync status reporting, but not remote exploitation or privilege escalation.

Researcher notes

The vulnerable behavior is a race between md_do_sync() updates and status_resync() reads. The fix handles overflow by reporting active resync instead of iterating over an invalidly large progress value. Source evidence does not define attacker prerequisites.

Mitigation direction

  • Apply vendor kernel updates containing the referenced stable md fix.
  • Check distribution advisories for package-specific fixed kernel versions.
  • Prioritize systems using Linux md software RAID.
  • Monitor affected hosts for soft lockup or hung task messages.
  • Plan maintenance windows for kernel updates requiring reboot.

Validation and detection

  • Inventory hosts using Linux md software RAID.
  • Check kernel version and vendor advisory status.
  • Confirm changelog includes “md: fix soft lockup in status_resync”.
  • Review kernel logs for md resync soft lockups.
  • Validate resync status reporting after applying updates.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-53620 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2unaffected
LinuxLinux2.6.12, 0, 6.1.30, 6.3.4, 6.4affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.