From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2025-22019: bcachefs: bch2_ioctl_subvolume_destroy() fixes
Date: Wed, 16 Apr 2025 12:20:41 +0200 [thread overview]
Message-ID: <2025041640-CVE-2025-22019-e865@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
bcachefs: bch2_ioctl_subvolume_destroy() fixes
bch2_evict_subvolume_inodes() was getting stuck - due to incorrectly
pruning the dcache.
Also, fix missing permissions checks.
The Linux kernel CVE team has assigned CVE-2025-22019 to this issue.
Affected and fixed versions
===========================
Fixed in 6.12.22 with commit 9e6e83e1e2d01b99e70cd7812d7f758a8def9fc8
Fixed in 6.13.10 with commit 82383abd39abd635511b8956284a5cc8134c4dc1
Fixed in 6.14.2 with commit 558317a5c61045d460a37372181e7b43c0c002bb
Fixed in 6.15-rc1 with commit 707549600c4a012ed71c0204a7992a679880bf33
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-2025-22019
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:
fs/bcachefs/fs-ioctl.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/9e6e83e1e2d01b99e70cd7812d7f758a8def9fc8
https://git.kernel.org/stable/c/82383abd39abd635511b8956284a5cc8134c4dc1
https://git.kernel.org/stable/c/558317a5c61045d460a37372181e7b43c0c002bb
https://git.kernel.org/stable/c/707549600c4a012ed71c0204a7992a679880bf33
reply other threads:[~2025-04-16 10:20 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=2025041640-CVE-2025-22019-e865@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.