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.
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.
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.
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.
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.
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.