LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54123: md/raid10: fix memleak for 'conf->bio_split'

In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix memleak for 'conf->bio_split' In the error path of raid10_run(), 'conf' need be freed, however, 'conf->bio_split' is missed and memory will be leaked. Since there are 3 places to free 'conf', factor out a helper to fix the problem.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel memory leak in the md RAID10 driver. When RAID10 initialization fails in raid10_run(), one allocated object, conf->bio_split, was not freed. The source bundle does not provide CVSS, exploitability, or observed attack evidence.

Executive priority

Handle through normal kernel patch management unless affected md RAID10 systems are business-critical or showing stability issues. The available evidence does not support emergency response, but storage infrastructure should not be ignored.

Technical view

The fix factors cleanup for the RAID10 configuration so all failure paths release conf->bio_split before freeing conf. The vulnerable area is md/raid10 in the Linux kernel. Public references are stable kernel commits, but the bundle does not describe attacker prerequisites or a complete affected-version matrix.

Likely exposure

Exposure is most likely on Linux systems using the md RAID10 kernel path and running an affected kernel revision. Systems not using md RAID10 are less likely to exercise this code path, based on the provided description.

Exploitation context

The bundle states KEV is false and provides no cited evidence of active exploitation. It describes a memory leak in an error path, not a public exploit technique. Do not treat this as exploited without additional vendor or KEV evidence.

Researcher notes

The CVE is narrow: md/raid10 leaks conf->bio_split in raid10_run() error handling. The bundle lacks CVSS, CWE, exploit prerequisites, and distro advisories. Analysis should focus on code reachability, kernel branch mapping, and vendor backport confirmation.

Mitigation direction

  • Identify Linux systems using md RAID10.
  • Compare running kernel versions against vendor advisories and stable kernel fixes.
  • Prioritize updates for important storage hosts using affected kernel branches.
  • Use distribution-provided kernel updates where available.
  • Monitor vendor guidance for backported fixes and corrected package versions.

Validation and detection

  • Inventory kernels and md RAID10 usage across production systems.
  • Check whether vendor kernel packages include the referenced stable fixes.
  • Review storage initialization failure logs for repeated RAID10 setup errors.
  • Confirm updated systems boot the fixed kernel.
  • Track this CVE in vulnerability management until vendor status is confirmed.
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-54123 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
LinuxLinuxfc9977dd069e4f82fcacb262652117c488647319, fc9977dd069e4f82fcacb262652117c488647319, fc9977dd069e4f82fcacb262652117c488647319, fc9977dd069e4f82fcacb262652117c488647319, fc9977dd069e4f82fcacb262652117c488647319, fc9977dd069e4f82fcacb262652117c488647319, fc9977dd069e4f82fcacb262652117c488647319, fc9977dd069e4f82fcacb262652117c488647319unaffected
LinuxLinux4.12, 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.