From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2023-54294: md/raid10: fix memleak of md thread
Date: Tue, 30 Dec 2025 13:23:47 +0100 [thread overview]
Message-ID: <2025123030-CVE-2023-54294-e7ac@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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().
The Linux kernel CVE team has assigned CVE-2023-54294 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.16 with commit 43a521238aca0e24d50add1db125a61bda2a3527 and fixed in 4.19.283 with commit abf4d67060c8f63caff096e5fca1564bfef1e5d4
Issue introduced in 4.16 with commit 43a521238aca0e24d50add1db125a61bda2a3527 and fixed in 5.4.243 with commit 3725b35fc0e5e4eea0434ef625f3d92f3059d080
Issue introduced in 4.16 with commit 43a521238aca0e24d50add1db125a61bda2a3527 and fixed in 5.10.180 with commit 2a65555f7e0f4a05b663879908a991e6d9f81e51
Issue introduced in 4.16 with commit 43a521238aca0e24d50add1db125a61bda2a3527 and fixed in 5.15.111 with commit d6cfcf98b824591cffa4c1e9889fb4fa619359fe
Issue introduced in 4.16 with commit 43a521238aca0e24d50add1db125a61bda2a3527 and fixed in 6.1.28 with commit 36ba0c7b86acd9c2ea80a273204d52c21c955471
Issue introduced in 4.16 with commit 43a521238aca0e24d50add1db125a61bda2a3527 and fixed in 6.2.15 with commit 5d763f708b0f918fb87799e33c25113ae6081216
Issue introduced in 4.16 with commit 43a521238aca0e24d50add1db125a61bda2a3527 and fixed in 6.3.2 with commit ec473e82e10d39a02eb59b0b95e546119a3bdb79
Issue introduced in 4.16 with commit 43a521238aca0e24d50add1db125a61bda2a3527 and fixed in 6.4 with commit f0ddb83da3cbbf8a1f9087a642c448ff52ee9abd
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2023-54294
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/md/raid10.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/abf4d67060c8f63caff096e5fca1564bfef1e5d4
https://git.kernel.org/stable/c/3725b35fc0e5e4eea0434ef625f3d92f3059d080
https://git.kernel.org/stable/c/2a65555f7e0f4a05b663879908a991e6d9f81e51
https://git.kernel.org/stable/c/d6cfcf98b824591cffa4c1e9889fb4fa619359fe
https://git.kernel.org/stable/c/36ba0c7b86acd9c2ea80a273204d52c21c955471
https://git.kernel.org/stable/c/5d763f708b0f918fb87799e33c25113ae6081216
https://git.kernel.org/stable/c/ec473e82e10d39a02eb59b0b95e546119a3bdb79
https://git.kernel.org/stable/c/f0ddb83da3cbbf8a1f9087a642c448ff52ee9abd
reply other threads:[~2025-12-30 12:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025123030-CVE-2023-54294-e7ac@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.