LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53299: md/raid10: fix leak of 'r10bio->remaining' for recovery

In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix leak of 'r10bio->remaining' for recovery raid10_sync_request() will add 'r10bio->remaining' for both rdev and replacement rdev. However, if the read io fails, recovery_request_write() returns without issuing the write io, in this case, end_sync_request() is only called once and 'remaining' is leaked, cause an io hang. Fix the problem by decreasing 'remaining' according to if 'bio' and 'repl_bio' is valid.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can make systems using md RAID10 hang during recovery after a read I/O failure. The impact is availability, not data theft or privilege escalation. It matters most for servers relying on software RAID10 where storage recovery operations are operationally critical.

Executive priority

Treat as a moderate infrastructure reliability issue. Prioritize patching storage-critical Linux servers using software RAID10, but do not escalate as an internet-facing compromise without additional evidence.

Technical view

In md/raid10 recovery, raid10_sync_request() increments r10bio->remaining for both the primary and replacement device. If read I/O fails, recovery_request_write() can return without issuing writes, so end_sync_request() is called only once and remaining is leaked, causing an I/O hang.

Likely exposure

Exposure is limited to Linux systems using the md RAID10 driver, especially during recovery or replacement-device workflows. CVSS requires local access and low privileges, with high availability impact. The bundle lists multiple Linux kernel versions as affected, but does not map distro package versions.

Exploitation context

The source bundle does not show active exploitation, and KEV is false. The plausible risk is local availability disruption when RAID10 recovery hits the described failed-read path. No source in the bundle supports remote exploitation or confidentiality impact.

Researcher notes

The key condition is a reference-count leak in r10bio->remaining after read failure prevents expected completion handling. Evidence is strong for root cause and availability impact, but the bundle does not provide exploit reports, distro fix matrices, or operational workarounds.

Mitigation direction

  • Apply vendor kernel updates containing the referenced md/raid10 stable fixes.
  • Prioritize systems using Linux md RAID10 for critical storage availability.
  • Check Linux distribution advisories for exact fixed package versions.
  • Schedule updates around storage maintenance windows and RAID recovery risk.
  • Avoid direct wrangler/deployment relevance; this is kernel infrastructure maintenance.

Validation and detection

  • Inventory hosts running Linux md RAID10 arrays.
  • Compare running kernels against vendor fixed package guidance.
  • Review whether RAID10 recovery or replacement operations are pending or recurring.
  • Monitor affected hosts for I/O hangs during md RAID recovery.
  • Confirm patched kernels include the referenced upstream stable commits.
Prepared
Confidence
high
Sources
11

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.

cwe · low confidence lookup

CWE-401: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-53299 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
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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.

1CVSS vectors
3Timeline events
1ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2023-53299Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux24afd80d99f80a79d8824d2805114b8b067e9823, 24afd80d99f80a79d8824d2805114b8b067e9823, 24afd80d99f80a79d8824d2805114b8b067e9823, 24afd80d99f80a79d8824d2805114b8b067e9823, 24afd80d99f80a79d8824d2805114b8b067e9823, 24afd80d99f80a79d8824d2805114b8b067e9823, 24afd80d99f80a79d8824d2805114b8b067e9823, 24afd80d99f80a79d8824d2805114b8b067e9823, 24afd80d99f80a79d8824d2805114b8b067e9823unaffected
LinuxLinux3.3, 0, 4.14.315, 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

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

CWE-401 · source CWE mapping

Missing Release of Memory after Effective Lifetime

Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.