selinux-refpolicy.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: "selinux-refpolicy@vger.kernel.org"  <selinux-refpolicy@vger.kernel.org>
Subject: strange execmem
Date: Tue, 26 Feb 2019 09:40:44 +1100	[thread overview]
Message-ID: <2945607.tWFyTVdlCF@liv> (raw)

I'm seeing strange audit messages like the following from cron jobs on a 
couple of systems.  Any idea what this might be about?  I don't expect grep to 
be needing execmem access and when I run a command matching the proctitle at 
the shell prompt it doesn't need it.

type=PROCTITLE msg=audit(26/02/19 00:00:07.426:1130782) : proctitle=grep -m 1 
-oP pid-file=\K.+$ 
type=SYSCALL msg=audit(26/02/19 00:00:07.426:1130782) : arch=x86_64 
syscall=mmap success=no exit=EACCES(Permission denied) a0=0x0 a1=0x10000 
a2=PROT_READ|PROT_WRITE|PROT_EXEC a3=MAP_PRIVATE|MAP_ANONYMOUS items=0 
ppid=6557 pid=6559 auid=unset uid=root gid=root euid=root suid=root fsuid=root 
egid=root sgid=root fsgid=root tty=(none) ses=unset comm=grep exe=/bin/grep 
subj=system_u:system_r:logrotate_t:s0 key=(null) 
type=AVC msg=audit(26/02/19 00:00:07.426:1130782) : avc:  denied  { execmem } 
for  pid=6559 comm=grep scontext=system_u:system_r:logrotate_t:s0 
tcontext=system_u:system_r:logrotate_t:s0 tclass=process permissive=0

-- 
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/




             reply	other threads:[~2019-02-25 22:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-25 22:40 Russell Coker [this message]
2019-02-26  6:49 ` strange execmem Dominick Grift
2019-02-28  5:37 ` Russell Coker

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=2945607.tWFyTVdlCF@liv \
    --to=russell@coker.com.au \
    --cc=selinux-refpolicy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).