From: Paul Moore <paul@paul-moore.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: selinux@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] selinux/selinux-pr-20260919
Date: Sat, 19 Sep 2026 22:07:14 -0400 [thread overview]
Message-ID: <932d0e418d78fa40b5d18951a34876ac@paul-moore.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]
Linus,
Three fixes for Linux v7.3-rcX:
- Ensure that the cached SELinux access decisions are correct.
- Fix the SELinux overlayfs code to properly track the top-level/user
information on multiple stacked overlayfs filesystems.
- Fix the SELinux overlayfs code to properly enforce mprotect() access
control policy on all of the different layers in multiple stacked
overlayfs filesystems.
Paul
--
The following changes since commit df2908090cda368b01ff43709f51890076c56157:
Linux 7.3-rc2 (2026-09-06 15:07:20 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
tags/selinux-pr-20260919
for you to fetch changes up to 78fc54b934bfb2c18aad8154c7302067146946f9:
selinux: recheck intermediate backing files on mprotect()
(2026-09-15 23:30:07 -0400)
----------------------------------------------------------------
selinux/stable-7.3 PR 20260919
----------------------------------------------------------------
Christian Göttsche (1):
selinux: always fill AVC decision in avc_has_perm_noaudit()
Karl Mehltretter (2):
selinux: preserve user SID across nested backing files
selinux: recheck intermediate backing files on mprotect()
security/selinux/avc.c | 5
security/selinux/hooks.c | 158 ++++++++++++++++++++++++++----
security/selinux/include/objsec.h | 10 +
3 files changed, 150 insertions(+), 23 deletions(-)
--
paul-moore.com
next reply other threads:[~2026-09-20 2:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 2:07 Paul Moore [this message]
2026-09-20 15:10 ` 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=932d0e418d78fa40b5d18951a34876ac@paul-moore.com \
--to=paul@paul-moore.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=selinux@vger.kernel.org \
--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®