CVE-2023-53832

md/raid10: fix null-ptr-deref in raid10_sync_request

N/A
Published: December 9, 2025 at 01:29 AM UTC
Updated: June 17, 2026 at 06:46 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.3%

Description

In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix null-ptr-deref in raid10_sync_request init_resync() inits mempool and sets conf->have_replacemnt at the beginning of sync, close_sync() frees the mempool when sync is completed. After [1] recovery might be skipped and init_resync() is called but close_sync() is not. null-ptr-deref occurs with r10bio->dev[i].repl_bio. The following is one way to reproduce the issue. 1) create a array, wait for resync to complete, mddev->recovery_cp is set to MaxSector. 2) recovery is woken and it is skipped. conf->have_replacement is set to 0 in init_resync(). close_sync() not called. 3) some io errors and rdev A is set to WantReplacement. 4) a new device is added and set to A's replacement. 5) recovery is woken, A have replacement, but conf->have_replacemnt is 0. r10bio->dev[i].repl_bio will not be alloced and null-ptr-deref occurs. Fix it by not calling init_resync() if recovery skipped. [1] commit 7e83ccbecd60 ("md/raid10: Allow skipping recovery when clean arrays are assembled")

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.10 ≤ v < 4.19.2833.10 ≤ v < 5.10.1803.10 ≤ v < 5.15.1113.10 ≤ v < 5.4.2433.10 ≤ v < 6.1.283.10 ≤ v < 6.2.153.10 ≤ v < 6.3.23.10 ≤ v < 6.43.107e83ccbecd608b971f340e951c9e84cd0343002f
Vendor states this is fixed in 14964127be77884003976a392c9faa9ebaabbbe1 (fixed)
Vendor states this is fixed in 38d33593260536840b49fd1dcac9aedfd14a9d42 (fixed)
Vendor states this is fixed in 68695084077e3de9d3e94e09238ace2b6f246446 (fixed)
Vendor states this is fixed in 99b503e4edc5938885d839cf0e7571963f75d800 (fixed)
Vendor states this is fixed in 9e9efc77efd1956cc244af975240f2513d78a371 (fixed)
Vendor states this is fixed in a405c6f0229526160aa3f177f65e20c86fce84c5 (fixed)
Vendor states this is fixed in b50fd1c3d9d0175aa29ff2706ef36cc178bc356a (fixed)
Vendor states this is fixed in bdbf104b1c91fbf38f82c522ebf75429f094292a (fixed)
Vendor states this is fixed in 3.10 (unaffected)
Vendor states this is fixed in 4.19.283 (unaffected)
Vendor states this is fixed in 5.10.180 (unaffected)
Vendor states this is fixed in 5.15.111 (unaffected)
Vendor states this is fixed in 5.4.243 (unaffected)
Vendor states this is fixed in 6.1.28 (unaffected)
Vendor states this is fixed in 6.2.15 (unaffected)
Vendor states this is fixed in 6.3.2 (unaffected)
Vendor states this is fixed in 6.4 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card