CVE-2023-54294
Description
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().
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A memory leak in the Linux kernel's md/raid10 driver can leave conf->thread unfreed when raid10_run() fails after setup_conf() succeeds.
Vulnerability
Description
A memory leak vulnerability exists in the Linux kernel's Multiple Device (MD) driver for RAID10. In the raid10_run() function, if setup_conf() successfully allocates conf->thread but a subsequent step fails before mddev->thread is set, the allocated memory is not freed in the error path. This results in a kernel memory leak [1][2][3].
Exploitation
To exploit this vulnerability, an attacker must be able to trigger raid10_run() in a way that forces a failure after setup_conf() completes. This could be achieved by attempting to create or assemble a RAID10 array with an invalid configuration or causing an error during the device initialization. The attack requires local access with sufficient privileges (typically root) to manage MD devices.
Impact
The impact is a gradual depletion of system memory due to the unreleased allocation. While this does not directly lead to privilege escalation or code execution, repeated exploitation could exhaust memory resources, potentially causing system instability or denial of service.
Mitigation
The vulnerability is fixed in Linux kernel commits [1][2][3]. The fix ensures that mddev->thread is set immediately after setup_conf() so that any subsequent failure will properly clean up the thread allocation. Users should apply the latest kernel updates to remediate this issue.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
8abf4d67060c83725b35fc0e52a65555f7e0fd6cfcf98b82436ba0c7b86ac5d763f708b0fec473e82e10df0ddb83da3cbVulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
8- git.kernel.org/stable/c/2a65555f7e0f4a05b663879908a991e6d9f81e51nvd
- git.kernel.org/stable/c/36ba0c7b86acd9c2ea80a273204d52c21c955471nvd
- git.kernel.org/stable/c/3725b35fc0e5e4eea0434ef625f3d92f3059d080nvd
- git.kernel.org/stable/c/5d763f708b0f918fb87799e33c25113ae6081216nvd
- git.kernel.org/stable/c/abf4d67060c8f63caff096e5fca1564bfef1e5d4nvd
- git.kernel.org/stable/c/d6cfcf98b824591cffa4c1e9889fb4fa619359fenvd
- git.kernel.org/stable/c/ec473e82e10d39a02eb59b0b95e546119a3bdb79nvd
- git.kernel.org/stable/c/f0ddb83da3cbbf8a1f9087a642c448ff52ee9abdnvd
News mentions
0No linked articles in our index yet.