LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53848: md/raid5-cache: fix a deadlock in r5l_exit_log()

In the Linux kernel, the following vulnerability has been resolved: md/raid5-cache: fix a deadlock in r5l_exit_log() Commit b13015af94cf ("md/raid5-cache: Clear conf->log after finishing work") introduce a new problem: // caller hold reconfig_mutex r5l_exit_log flush_work(&log->disable_writeback_work) r5c_disable_writeback_async wait_event /* * conf->log is not NULL, and mddev_trylock() * will fail, wait_event() can never pass. */ conf->log = NULL Fix this problem by setting 'config->log' to NULL before wake_up() as it used to be, so that wait_event() from r5c_disable_writeback_async() can exist. In the meantime, move forward md_unregister_thread() so that null-ptr-deref this commit fixed can still be fixed.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can deadlock systems using md RAID5 cache during log shutdown or reconfiguration. The known impact from the provided sources is reliability and availability, not data theft. Public severity scoring is absent, so urgency should be driven by whether affected kernels and RAID5 cache are present in production.

Executive priority

Treat as a targeted availability risk, not a confirmed emergency. Patch during the next controlled kernel maintenance window, faster for production storage nodes using Linux md RAID5 cache.

Technical view

The flaw is a deadlock in md/raid5-cache r5l_exit_log(). With reconfig_mutex held, disable_writeback_work can wait forever because conf->log remains non-NULL and mddev_trylock() fails. The fix restores setting conf->log to NULL before wake_up() and moves md_unregister_thread() earlier to preserve a null-pointer-dereference fix.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with md RAID5 cache functionality. The bundle lists Linux 6.0, 6.1.53, 6.4.16, 6.5.3, and 6.6 as affected, but distribution backports may change practical exposure.

Exploitation context

The source bundle marks KEV as false and provides no evidence of active exploitation or public exploit use. The issue is described as a kernel deadlock regression, so the clearest risk is operational disruption on affected RAID5-cache configurations.

Researcher notes

Evidence is limited to the CVE description and upstream stable commit references. There is no CVSS, CWE, exploit confirmation, or detailed distribution impact in the bundle. Avoid broad claims beyond md/raid5-cache deadlock behavior and listed affected Linux versions.

Mitigation direction

  • Apply Linux vendor kernel updates that include the referenced stable fixes.
  • Prioritize systems using md RAID5 or raid5-cache in production.
  • Check distribution advisories for fixed package versions and backport status.
  • If patching is delayed, consult vendor guidance for supported operational workarounds.

Validation and detection

  • Inventory Linux kernel versions across systems using software RAID.
  • Identify hosts using md RAID5 cache features.
  • Confirm installed kernels include one of the referenced stable fixes or vendor backports.
  • Review vendor advisories because upstream version labels may not match distribution packages.
Prepared
Confidence
medium
Sources
6

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-53848 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
5Source 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
LinuxLinuxb13015af94cf405f73ff64ce0797269554020c37, b13015af94cf405f73ff64ce0797269554020c37, b13015af94cf405f73ff64ce0797269554020c37, b13015af94cf405f73ff64ce0797269554020c37unaffected
LinuxLinux6.0, 0, 6.1.53, 6.4.16, 6.5.3, 6.6affected
Weakness

CWE details

No CWE listed

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