public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: George McCollister <george.mccollister@gmail.com>
Cc: linux-audit@redhat.com
Subject: Re: [userspace PATCH] Prevent free() of stack buffer with NOLOG format
Date: Tue, 06 Dec 2016 10:55:05 -0500	[thread overview]
Message-ID: <1613616.fOQnUE7urM@x2> (raw)
In-Reply-To: <CAFSKS=OdaX5wAJN7j2i9vQq9kU6A=zsbz9V0R3K1sqfDz4=Faw@mail.gmail.com>

On Tuesday, December 6, 2016 7:57:33 AM EST George McCollister wrote:
> On Mon, Dec 5, 2016 at 6:30 PM, Steve Grubb <sgrubb@redhat.com> wrote:
> > On Monday, December 5, 2016 6:01:02 PM EST George McCollister wrote:
> >> When the NOLOG format is used replace_event_msg() doesn't change
> >> e->reply.message so the message located on the stack is left and later is
> > 
> >> free()'d in cleanup_event() resulting in the following:
> > Hmm...thanks for reporting this. Which version of audit are you using?
> 
> I'm using 2.6.6 but I reproduced the problem and made the change
> against the HEAD of the master branch (using this mirror
> https://github.com/linux-audit/audit-userspace).

OK. Got it. The patch isn't exactly the right fix. While it may hide the 
problem, the intent is that people may want to use the enriched format and 
send logs to a remote collector. By any chance do you know which buffer on the 
stack is getting freed? I'm trying to reproduce this but I thought I'd ask if 
you where it is since you have already looked into it.

Thanks,
-Steve

  reply	other threads:[~2016-12-06 15:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-06  0:01 [userspace PATCH] Prevent free() of stack buffer with NOLOG format George McCollister
2016-12-06  0:30 ` Steve Grubb
2016-12-06 13:57   ` George McCollister
2016-12-06 15:55     ` Steve Grubb [this message]
2016-12-07 14:39       ` Steve Grubb

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=1613616.fOQnUE7urM@x2 \
    --to=sgrubb@redhat.com \
    --cc=george.mccollister@gmail.com \
    --cc=linux-audit@redhat.com \
    /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