All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: selinux@vger.kernel.org
Subject: Re: [PATCH] selinux: add proper NULL termination to the secclass_map permissions
Date: Thu, 22 Apr 2021 22:19:08 -0400	[thread overview]
Message-ID: <CAHC9VhTdSU_M1m4TJiE2edVXb-oDRA=ZhQv1AsPmAk6u5HknPg@mail.gmail.com> (raw)
In-Reply-To: <161906228493.81125.6079062739552342511.stgit@olly>

On Wed, Apr 21, 2021 at 11:31 PM Paul Moore <paul@paul-moore.com> wrote:
>
> This patch adds the missing NULL termination to the "bpf" and
> "perf_event" object class permission lists.
>
> This missing NULL termination should really only affect the tools
> under scripts/selinux, with the most important being genheaders.c,
> although in practice this has not been an issue on any of my dev/test
> systems.  If the problem were to manifest itself it would likely
> result in bogus permissions added to the end of the object class;
> thankfully with no access control checks using these bogus
> permissions and no policies defining these permissions the impact
> would likely be limited to some noise about undefined permissions
> during policy load.
>
> Cc: stable@vger.kernel.org
> Fixes: ec27c3568a34 ("selinux: bpf: Add selinux check for eBPF syscall operations")
> Fixes: da97e18458fb ("perf_event: Add support for LSM and SELinux checks")
> Signed-off-by: Paul Moore <paul@paul-moore.com>
> ---
>  security/selinux/include/classmap.h |    5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)

I just merged this into selinux/next, and given that we are at -rc8 I
felt a bit of an explanation was a good idea.

Typically fixes like this would be merged via the current
selinux/stable-X.YY branch and sent to Linus via a PR after a few days
of soaking and test runs.  However, with the v5.12 release likely this
weekend, only a few days away, it seems overly risky to send this to
Linus now when one considers the nature of the patch and the fact that
we can send it to Linus as part of the v5.13 merge window next week.

-- 
paul moore
www.paul-moore.com

      reply	other threads:[~2021-04-23  2:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22  3:31 [PATCH] selinux: add proper NULL termination to the secclass_map permissions Paul Moore
2021-04-23  2:19 ` Paul Moore [this message]

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='CAHC9VhTdSU_M1m4TJiE2edVXb-oDRA=ZhQv1AsPmAk6u5HknPg@mail.gmail.com' \
    --to=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.