From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2025-21691: cachestat: fix page cache statistics permission checking
Date: Mon, 10 Feb 2025 16:58:59 +0100 [thread overview]
Message-ID: <2025021055-CVE-2025-21691-2bd2@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
cachestat: fix page cache statistics permission checking
When the 'cachestat()' system call was added in commit cf264e1329fb
("cachestat: implement cachestat syscall"), it was meant to be a much
more convenient (and performant) version of mincore() that didn't need
mapping things into the user virtual address space in order to work.
But it ended up missing the "check for writability or ownership" fix for
mincore(), done in commit 134fca9063ad ("mm/mincore.c: make mincore()
more conservative").
This just adds equivalent logic to 'cachestat()', modified for the file
context (rather than vma).
The Linux kernel CVE team has assigned CVE-2025-21691 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.5 with commit cf264e1329fb0307e044f7675849f9f38b44c11a and fixed in 6.6.75 with commit 7d6405c13b0d8a8367cd8df63f118b619a3f0dd2
Issue introduced in 6.5 with commit cf264e1329fb0307e044f7675849f9f38b44c11a and fixed in 6.12.12 with commit 780ab8329672464984cf1344bd5c3993af0226c7
Issue introduced in 6.5 with commit cf264e1329fb0307e044f7675849f9f38b44c11a and fixed in 6.13.1 with commit 97153a05077f618f7471f50a78158602badccb30
Issue introduced in 6.5 with commit cf264e1329fb0307e044f7675849f9f38b44c11a and fixed in 6.14-rc1 with commit 5f537664e705b0bf8b7e329861f20128534f6a83
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-21691
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:
mm/filemap.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/7d6405c13b0d8a8367cd8df63f118b619a3f0dd2
https://git.kernel.org/stable/c/780ab8329672464984cf1344bd5c3993af0226c7
https://git.kernel.org/stable/c/97153a05077f618f7471f50a78158602badccb30
https://git.kernel.org/stable/c/5f537664e705b0bf8b7e329861f20128534f6a83
reply other threads:[~2025-02-10 15:59 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=2025021055-CVE-2025-21691-2bd2@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.