LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54294: md/raid10: fix memleak of md thread

In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix memleak of md thread In raid10_run(), if setup_conf() succeed and raid10_run() failed before setting 'mddev->thread', then in the error path 'conf->thread' is not freed. Fix the problem by setting 'mddev->thread' right after setup_conf().

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel RAID10 cleanup bug. If RAID10 startup fails at a narrow point, the kernel can leave an md thread allocated instead of freeing it. The public record does not provide CVSS, observed exploitation, or evidence of direct data compromise.

Executive priority

Handle through normal kernel maintenance unless critical RAID10 infrastructure is affected. There is no source-backed evidence of active exploitation, but storage hosts should stay current because kernel memory leaks can affect reliability.

Technical view

In md/raid10 raid10_run(), when setup_conf() succeeds but raid10_run() fails before mddev->thread is assigned, conf->thread is not freed on the error path. The referenced kernel fixes assign mddev->thread immediately after setup_conf() so the failure path can clean it up.

Likely exposure

Exposure is most relevant to Linux systems using the kernel md RAID10 driver. The source lists Linux kernel versions and stable-branch fixes, but does not provide distribution package names or appliance mappings.

Exploitation context

The bundle marks KEV false and provides no cited evidence of active exploitation. The described impact is a memory leak during a RAID10 startup failure path, not a remote code execution or privilege escalation claim.

Researcher notes

The record is sparse: no CVSS, CWE, exploit status, or distribution advisories are included. Analysis should stay limited to the md/raid10 error-path memory leak and the stable kernel commits referenced by the CVE data.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable fixes.
  • Prioritize systems using md RAID10 or storage-heavy Linux hosts.
  • Check Linux distribution advisories for backported fixes.
  • Plan reboots where required to activate updated kernels.

Validation and detection

  • Inventory Linux systems using md RAID10.
  • Compare running kernels against vendor fixed package guidance.
  • Confirm changelogs reference CVE-2023-54294 or the listed stable commits.
  • After patching, verify the updated kernel is active.
Prepared
Confidence
medium
Sources
10

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-54294 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
9Source 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
LinuxLinux43a521238aca0e24d50add1db125a61bda2a3527, 43a521238aca0e24d50add1db125a61bda2a3527, 43a521238aca0e24d50add1db125a61bda2a3527, 43a521238aca0e24d50add1db125a61bda2a3527, 43a521238aca0e24d50add1db125a61bda2a3527, 43a521238aca0e24d50add1db125a61bda2a3527, 43a521238aca0e24d50add1db125a61bda2a3527, 43a521238aca0e24d50add1db125a61bda2a3527unaffected
LinuxLinux4.16, 0, 4.19.283, 5.4.243, 5.10.180, 5.15.111, 6.1.28, 6.2.15, 6.3.2, 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.