From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49384: md: fix double free of io_acct_set bioset
Date: Wed, 26 Feb 2025 03:10:58 +0100 [thread overview]
Message-ID: <2025022648-CVE-2022-49384-422b@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
md: fix double free of io_acct_set bioset
Now io_acct_set is alloc and free in personality. Remove the codes that
free io_acct_set in md_free and md_stop.
The Linux kernel CVE team has assigned CVE-2022-49384 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.15.17 with commit 00e3d58f50a875343124bcf5a9637520a492b0d1 and fixed in 5.15.46 with commit 36a2fc44c574a59ee3b5e2cb327182f227b2b07e
Issue introduced in 5.17 with commit 0c031fd37f69deb0cd8c43bbfcfccd62ebd7e952 and fixed in 5.17.14 with commit f99d5b5dc8a42c807b5f1176b925aa45d61962ab
Issue introduced in 5.17 with commit 0c031fd37f69deb0cd8c43bbfcfccd62ebd7e952 and fixed in 5.18.3 with commit ea7d7bd90079d96f9c86bdaf0b106e0cd2a70661
Issue introduced in 5.17 with commit 0c031fd37f69deb0cd8c43bbfcfccd62ebd7e952 and fixed in 5.19 with commit 42b805af102471f53e3c7867b8c2b502ea4eef7e
Issue introduced in 5.16.3 with commit 92053ae0398a58c6914e807d5e070297ba8cfe88
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-2022-49384
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/md.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/36a2fc44c574a59ee3b5e2cb327182f227b2b07e
https://git.kernel.org/stable/c/f99d5b5dc8a42c807b5f1176b925aa45d61962ab
https://git.kernel.org/stable/c/ea7d7bd90079d96f9c86bdaf0b106e0cd2a70661
https://git.kernel.org/stable/c/42b805af102471f53e3c7867b8c2b502ea4eef7e
reply other threads:[~2025-02-26 2:14 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=2025022648-CVE-2022-49384-422b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@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.