From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 22624216600 for ; Wed, 26 Feb 2025 02:14:03 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740536043; cv=none; b=nS7vpLiTo2hveUs6lis7VfIDtR4tkYA38sLChX5ygskUTBCzopJhUaC8IgGIGo6p7zFLBs21p+3JmnVue72A6ygXT0515fYaklf0qHFGYfCud6ILq3oxT6nO+ZwNeR4aMvOwpe1UPyg48fcxbw00mbLpJy9DVJ0ov/5YRdtTpBM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740536043; c=relaxed/simple; bh=kmVZFAaAtnfKzp6bH9rUZlnqBS42RgqiyoDcfWeqAGs=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=gctlqIWUvYm/gF/3KSJm63yHJVXso9Fm+8P5hHflzoYSq/ekpdEmsaIcCjW8U2mc6pHcIKg2jnUOoIbTj1LYjSV6YKFFm37b6iB5V0Koei5JVdIiE/A1ts6R/Kx8NsNM2/uUjLpRrwJs/Gd7Th3OC+rg5ctnOs478VQETUq1f9w= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=ooFIqI41; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="ooFIqI41" Received: by smtp.kernel.org (Postfix) with ESMTPSA id ED0B9C4CEDD; Wed, 26 Feb 2025 02:14:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1740536043; bh=kmVZFAaAtnfKzp6bH9rUZlnqBS42RgqiyoDcfWeqAGs=; h=From:To:Cc:Subject:Date:Reply-to:From; b=ooFIqI41bWErFk6IwdkmSZjJw8ibuqUcStzmzMzd5rdYFfPZSQ5ps93nfNlAgs1cC KM/qhI3n+WVOZasWtxtYfsjiLlKk0KaJKcCuUtz/d/tgsfECUWYONQkvl3Yw/CtnSE zNARXSvLIAlyCQz1XBVmlKP0sIAHc0U4oO2XuMV8= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2022-49413: bfq: Update cgroup information before merging bio Date: Wed, 26 Feb 2025 03:11:27 +0100 Message-ID: <2025022653-CVE-2022-49413-ae69@gregkh> X-Mailer: git-send-email 2.48.1 Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Reply-to: , X-Developer-Signature: v=1; a=openpgp-sha256; l=3147; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=kmVZFAaAtnfKzp6bH9rUZlnqBS42RgqiyoDcfWeqAGs=; b=owGbwMvMwCRo6H6F97bub03G02pJDOn7yj/+2e6yLmLKj7uf1rTyB8azvzTnkBerO6H5ROnXw 5b4gu/8HbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjCRxGyGeWY3NqYqNXfrVMzI WyRZYhO6PpPzKcM8m/MThWVnxhp3+0w68mjeEialwP4kAA== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit 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