From: Mike Rapoport <rppt@kernel.org>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
Kees Cook <kees@kernel.org>,
linux-kernel@vger.kernel.org, Will Drewry <wad@chromium.org>,
Christian Brauner <brauner@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: [PATCH v4 0/6] seccomp: non-cooperative pinned-memfd argument redirect
Date: Sat, 27 Jun 2026 11:19:03 +0300 [thread overview]
Message-ID: <178254834314.5812.2094612523351837049.b4-reply@b4> (raw)
In-Reply-To: <20260627012219.1079851-1-xiyou.wangcong@gmail.com>
On 2026-06-26 18:22 -0700, Cong Wang wrote:
> The seccomp user-notification SECCOMP_USER_NOTIF_FLAG_CONTINUE response
> carries an inherent TOCTOU: once the supervisor decides to let a syscall
> continue, the target (or a CLONE_VM peer) can rewrite the memory behind a
> pointer argument before the kernel reads it. This is documented in the
> UAPI header and is why the notifier "cannot be used to implement a
> security policy" today.
>
> ---
> Cong Wang (6):
> mm: add __do_mmap() and vm_mmap_seal_remote()
> seccomp: introduce SECCOMP_IOCTL_NOTIF_PIN_INSTALL
> seccomp: add kernel-installed pinned-memfd redirect
> seccomp: re-validate a redirected syscall against outer filters
> selftests/seccomp: cover non-cooperative pinned-memfd install
> docs/seccomp: document pinned-memfd redirect ioctls
This breaks VMA tests:
https://github.com/linux-mm/linux-mm/actions/runs/28274564619/job/83778604364
next prev parent reply other threads:[~2026-06-27 8:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-27 1:22 Cong Wang
2026-06-27 1:22 ` [PATCH v4 1/6] mm: add __do_mmap() and vm_mmap_seal_remote() Cong Wang
2026-06-27 1:22 ` [PATCH v4 2/6] seccomp: introduce SECCOMP_IOCTL_NOTIF_PIN_INSTALL Cong Wang
2026-06-27 1:22 ` [PATCH v4 3/6] seccomp: add kernel-installed pinned-memfd redirect Cong Wang
2026-06-27 1:22 ` [PATCH v4 4/6] seccomp: re-validate a redirected syscall against outer filters Cong Wang
2026-06-27 1:22 ` [PATCH v4 5/6] selftests/seccomp: cover non-cooperative pinned-memfd install Cong Wang
2026-06-27 1:22 ` [PATCH v4 6/6] docs/seccomp: document pinned-memfd redirect ioctls Cong Wang
2026-06-27 4:43 ` [PATCH v4 0/6] seccomp: non-cooperative pinned-memfd argument redirect Andrew Morton
2026-07-01 20:37 ` Cong Wang
2026-06-27 8:19 ` Mike Rapoport [this message]
2026-07-01 20:40 ` Cong Wang
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=178254834314.5812.2094612523351837049.b4-reply@b4 \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@amacapital.net \
--cc=wad@chromium.org \
--cc=xiyou.wangcong@gmail.com \
/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
all inboxes | Powered by JetHome®