From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Eyal Birger <eyal.birger@gmail.com>,
Kees Cook <kees@kernel.org>, Rafael Buchbinder <rafi@rbk.io>
Subject: [GIT PULL] seccomp fix for v6.14-rc2
Date: Sat, 8 Feb 2025 12:34:06 -0800 [thread overview]
Message-ID: <202502081231.AC11AB4@keescook> (raw)
Hi Linus,
Please pull this seccomp fix for v6.14-rc2. This is really a work-around
for x86_64 having grown a syscall to implement uretprobe, which has
caused problems since v6.11. This may change in the future, but for now,
this fixes the unintended seccomp filtering when uretprobe switched away
from traps, and does so with something that should be easy to backport.
Thanks!
-Kees
The following changes since commit 2014c95afecee3e76ca4a56956a936e23283f05b:
Linux 6.14-rc1 (2025-02-02 15:39:26 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-v6.14-rc2
for you to fetch changes up to c2debdb8544f415eaf9292a866d4073912eeb561:
selftests/seccomp: validate uretprobe syscall passes through seccomp (2025-02-06 13:19:14 -0800)
----------------------------------------------------------------
seccomp fix for v6.14-rc2
- Allow uretprobe on x86_64 to avoid behavioral complications (Eyal Birger)
----------------------------------------------------------------
Eyal Birger (2):
seccomp: passthrough uretprobe systemcall without filtering
selftests/seccomp: validate uretprobe syscall passes through seccomp
kernel/seccomp.c | 12 ++
tools/testing/selftests/seccomp/seccomp_bpf.c | 199 ++++++++++++++++++++++++++
2 files changed, 211 insertions(+)
--
Kees Cook
next reply other threads:[~2025-02-08 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 20:34 Kees Cook [this message]
2025-02-08 22:25 ` 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=202502081231.AC11AB4@keescook \
--to=kees@kernel.org \
--cc=eyal.birger@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafi@rbk.io \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®