From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: fsverity@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-security-module@vger.kernel.org,
Theodore Ts'o <tytso@mit.edu>, Fan Wu <wufan@kernel.org>
Subject: [GIT PULL] fsverity fixes for v7.4-rc1
Date: Fri, 30 Oct 2026 13:24:15 -0700 [thread overview]
Message-ID: <20261030202415.GA1967@quark> (raw)
The following changes since commit 8a36f53fd5ec3eff01f1b637d42cbdc3821d0493:
Merge tag 'mm-stable-2026-10-25-19-27' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm (2026-10-27 12:23:17 -1000)
are available in the Git repository at:
https://git.kernel.org/pub/scm/fs/fsverity/linux.git tags/fsverity-for-linus
for you to fetch changes up to c349b233d6ab0fc3517401a1e2d36f5f90eb8c9b:
fsverity: Set S_VERITY only after rollback is no longer possible (2026-10-28 10:53:43 -0700)
----------------------------------------------------------------
Fixes for several bugs found by LLMs:
- Fix bypass of IPE's fsverity support, and a use-after-free in
certain cases, when FS_IOC_ENABLE_VERITY fails when almost done.
- Fix FS_IOC_MEASURE_VERITY and FS_IOC_READ_VERITY_METADATA to no
longer bypass Landlock and AppArmor's read permission checks.
- Be robust against the filesystem returning different values for a
file's verity descriptor length in two successive queries.
----------------------------------------------------------------
Eric Biggers (4):
fsverity: Explicitly require FMODE_READ to retrieve hashes
fsverity: Be more careful with return value of ->get_verity_descriptor()
fsverity: Tell LSMs about signature only after verity is enabled
fsverity: Set S_VERITY only after rollback is no longer possible
Documentation/filesystems/fsverity.rst | 3 ++
fs/btrfs/verity.c | 7 +++--
fs/ext4/verity.c | 4 ++-
fs/verity/enable.c | 20 ++++++++-----
fs/verity/fsverity_private.h | 8 +++++
fs/verity/measure.c | 10 +++++++
fs/verity/open.c | 47 +++++++++++++++++------------
fs/verity/read_metadata.c | 14 ++++++---
fs/verity/signature.c | 55 ++++++++++++++++++++++++----------
include/linux/fsverity.h | 12 ++++----
10 files changed, 126 insertions(+), 54 deletions(-)
next reply other threads:[~2026-10-30 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 20:24 Eric Biggers [this message]
2026-10-31 0:10 ` [GIT PULL] fsverity fixes for v7.4-rc1 pr-tracker-bot
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=20261030202415.GA1967@quark \
--to=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=wufan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox