From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49411: bfq: Make sure bfqg for which we are queueing requests is online
Date: Wed, 26 Feb 2025 03:11:25 +0100 [thread overview]
Message-ID: <2025022652-CVE-2022-49411-63ad@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
bfq: Make sure bfqg for which we are queueing requests is online
Bios queued into BFQ IO scheduler can be associated with a cgroup that
was already offlined. This may then cause insertion of this bfq_group
into a service tree. But this bfq_group will get freed as soon as last
bio associated with it is completed leading to use after free issues for
service tree users. Fix the problem by making sure we always operate on
online bfq_group. If the bfq_group associated with the bio is not
online, we pick the first online parent.
The Linux kernel CVE team has assigned CVE-2022-49411 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.12 with commit e21b7a0b988772e82e7147e1c659a5afe2ae003c and fixed in 5.4.198 with commit ccddf8cd411c1800863ed357064e56ceffd356bb
Issue introduced in 4.12 with commit e21b7a0b988772e82e7147e1c659a5afe2ae003c and fixed in 5.10.121 with commit 51f724bffa3403a5236597e6b75df7329c1ec6e9
Issue introduced in 4.12 with commit e21b7a0b988772e82e7147e1c659a5afe2ae003c and fixed in 5.15.46 with commit 6ee0868b0c3ccead5907685fcdcdd0c08dfe4b0b
Issue introduced in 4.12 with commit e21b7a0b988772e82e7147e1c659a5afe2ae003c and fixed in 5.17.14 with commit 97bd6c56bdcb41079e488e31df56809e3b2ce628
Issue introduced in 4.12 with commit e21b7a0b988772e82e7147e1c659a5afe2ae003c and fixed in 5.18.3 with commit 7781c38552e6cc54ed8e9040279561340516b881
Issue introduced in 4.12 with commit e21b7a0b988772e82e7147e1c659a5afe2ae003c and fixed in 5.19 with commit 075a53b78b815301f8d3dd1ee2cd99554e34f0dd
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-49411
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-cgroup.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/ccddf8cd411c1800863ed357064e56ceffd356bb
https://git.kernel.org/stable/c/51f724bffa3403a5236597e6b75df7329c1ec6e9
https://git.kernel.org/stable/c/6ee0868b0c3ccead5907685fcdcdd0c08dfe4b0b
https://git.kernel.org/stable/c/97bd6c56bdcb41079e488e31df56809e3b2ce628
https://git.kernel.org/stable/c/7781c38552e6cc54ed8e9040279561340516b881
https://git.kernel.org/stable/c/075a53b78b815301f8d3dd1ee2cd99554e34f0dd
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=2025022652-CVE-2022-49411-63ad@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.