From: "Serge E. Hallyn" <serge@hallyn.com>
To: Paul Moore <paul@paul-moore.com>
Cc: "Christian Göttsche" <cgoettsche@seltendoof.de>,
linux-kernel@vger.kernel.org,
"Christian Göttsche" <cgzones@googlemail.com>,
"Christian Brauner" <brauner@kernel.org>,
linux-security-module@vger.kernel.org, selinux@vger.kernel.org
Subject: Re: [PATCH] pid: use ns_capable_noaudit() when determining net sysctl permissions
Date: Thu, 11 Sep 2025 18:05:05 -0500 [thread overview]
Message-ID: <aMNVoSM7PauOrCPF@mail.hallyn.com> (raw)
In-Reply-To: <23663be0b8dc2a435bcc46a3d52e9e19@paul-moore.com>
On Thu, Sep 11, 2025 at 04:46:20PM -0400, Paul Moore wrote:
> On Sep 10, 2025 =?UTF-8?q?Christian=20G=C3=B6ttsche?= <cgoettsche@seltendoof.de> wrote:
> >
> > The capability check should not be audited since it is only being used
> > to determine the inode permissions. A failed check does not indicate a
> > violation of security policy but, when an LSM is enabled, a denial audit
> > message was being generated.
> >
> > The denial audit message can either lead to the capability being
> > unnecessarily allowed in a security policy, or being silenced potentially
> > masking a legitimate capability check at a later point in time.
> >
> > Similar to commit d6169b0206db ("net: Use ns_capable_noaudit() when
> > determining net sysctl permissions")
> >
> > Fixes: 7863dcc72d0f ("pid: allow pid_max to be set per pid namespace")
> > CC: Christian Brauner <brauner@kernel.org>
> > CC: linux-security-module@vger.kernel.org
> > CC: selinux@vger.kernel.org
> > Signed-off-by: Christian Göttsche <cgzones@googlemail.com>
> > ---
> > kernel/pid.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Reviewed-by: Paul Moore <paul@paul-moore.com>
Thanks.
Acked-by: Serge Hallyn <serge@hallyn.com>
I'll queue this up in the capability tree, unless Christian wanted
it in his.
-serge
next prev parent reply other threads:[~2025-09-11 23:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 19:26 [PATCH] pid: use ns_capable_noaudit() when determining net sysctl permissions Christian Göttsche
2025-09-11 20:46 ` Paul Moore
2025-09-11 23:05 ` Serge E. Hallyn [this message]
2025-09-12 19:35 ` Serge E. Hallyn
2025-09-15 14:13 ` Christian Brauner
2025-09-15 14:50 ` Serge E. Hallyn
2025-09-15 17:13 ` Serge E. Hallyn
2025-09-19 11:08 ` Christian Brauner
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=aMNVoSM7PauOrCPF@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=brauner@kernel.org \
--cc=cgoettsche@seltendoof.de \
--cc=cgzones@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=selinux@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.