From: "Serge E. Hallyn" <serge@hallyn.com>
To: torvalds@linux-foundation.org,
linux-security-module@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ariel Otilibili <ariel.otilibili-anieli@eurecom.fr>,
"Andrew G. Morgan" <morgan@kernel.org>,
Paul Moore <paul@paul-moore.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Max Kellermann <max.kellermann@ionos.com>,
Jann Horn <jannh@google.com>, Kees Cook <kees@kernel.org>
Subject: [GIT PULL] capabilities update for v6.17-rc1
Date: Tue, 29 Jul 2025 14:23:07 -0500 [thread overview]
Message-ID: <aIkfm1AGBoINgSRF@mail.hallyn.com> (raw)
The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:
Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/sergeh/linux.git tags/caps-pr-20250729
for you to fetch changes up to cdd73b1666079a73d061396f361df55d59fe96e6:
uapi: fix broken link in linux/capability.h (2025-07-04 19:21:53 -0500)
----------------------------------------------------------------
Capabilities update for 6.17
This branch contains two patches:
cdd73b1666079a73d061396f361df55d59fe96e6 uapi: fix broken link in linux/capability.h
This updates documentation in capability.h.
337490f0007f910968f828e46501db3091b1a4f8 exec: Correct the permission check for unsafe exec
This is not a trivial patch, but fixes a real problem where during
exec, different effective and real credentials were assumed to mean
changed credentials, making it impossible in the no-new-privs case
to keep different uid and euid.
These are available at:
git://git.kernel.org/pub/scm/linux/kernel/git/sergeh/linux.git #caps-pr-20250729
on top of commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494 (tag: v6.16-rc1)
----------------------------------------------------------------
Ariel Otilibili (1):
uapi: fix broken link in linux/capability.h
Eric W. Biederman (1):
exec: Correct the permission check for unsafe exec
include/uapi/linux/capability.h | 5 +++--
security/commoncap.c | 20 ++++++++------------
2 files changed, 11 insertions(+), 14 deletions(-)
next reply other threads:[~2025-07-29 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 19:23 Serge E. Hallyn [this message]
2025-07-31 19:07 ` 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=aIkfm1AGBoINgSRF@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=ariel.otilibili-anieli@eurecom.fr \
--cc=ebiederm@xmission.com \
--cc=jannh@google.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=max.kellermann@ionos.com \
--cc=morgan@kernel.org \
--cc=paul@paul-moore.com \
--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®