From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49413: bfq: Update cgroup information before merging bio
Date: Wed, 26 Feb 2025 03:11:27 +0100 [thread overview]
Message-ID: <2025022653-CVE-2022-49413-ae69@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
bfq: Update cgroup information before merging bio
When the process is migrated to a different cgroup (or in case of
writeback just starts submitting bios associated with a different
cgroup) bfq_merge_bio() can operate with stale cgroup information in
bic. Thus the bio can be merged to a request from a different cgroup or
it can result in merging of bfqqs for different cgroups or bfqqs of
already dead cgroups and causing possible use-after-free issues. Fix the
problem by updating cgroup information in bfq_merge_bio().
The Linux kernel CVE team has assigned CVE-2022-49413 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.12 with commit e21b7a0b988772e82e7147e1c659a5afe2ae003c and fixed in 5.4.198 with commit da9f3025d595956410ceaab2bea01980d7775948
Issue introduced in 4.12 with commit e21b7a0b988772e82e7147e1c659a5afe2ae003c and fixed in 5.10.121 with commit b06691af08b41dfd81052a3362514d9827b44bb1
Issue introduced in 4.12 with commit e21b7a0b988772e82e7147e1c659a5afe2ae003c and fixed in 5.15.46 with commit e8821f45612f2e6d9adb9c6ba0fb4184f57692aa
Issue introduced in 4.12 with commit e21b7a0b988772e82e7147e1c659a5afe2ae003c and fixed in 5.17.14 with commit d9165200c5627a2cf4408eefabdf0058bdf95e1a
Issue introduced in 4.12 with commit e21b7a0b988772e82e7147e1c659a5afe2ae003c and fixed in 5.18.3 with commit 2a1077f17169a6059992a0bbdb330e0abad1e6d9
Issue introduced in 4.12 with commit e21b7a0b988772e82e7147e1c659a5afe2ae003c and fixed in 5.19 with commit ea591cd4eb270393810e7be01feb8fde6a34fbbe
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-49413
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:
block/bfq-iosched.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/da9f3025d595956410ceaab2bea01980d7775948
https://git.kernel.org/stable/c/b06691af08b41dfd81052a3362514d9827b44bb1
https://git.kernel.org/stable/c/e8821f45612f2e6d9adb9c6ba0fb4184f57692aa
https://git.kernel.org/stable/c/d9165200c5627a2cf4408eefabdf0058bdf95e1a
https://git.kernel.org/stable/c/2a1077f17169a6059992a0bbdb330e0abad1e6d9
https://git.kernel.org/stable/c/ea591cd4eb270393810e7be01feb8fde6a34fbbe
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=2025022653-CVE-2022-49413-ae69@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.