From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oleg Nesterov Subject: Re: Report Double Fetch Bug Found in Linux-4.6.1/kernel/auditsc.c Date: Mon, 20 Jun 2016 21:18:14 +0200 Message-ID: <20160620191814.GA2942@redhat.com> References: <20160620182215.GC25615@madcap2.tricolour.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20160620182215.GC25615@madcap2.tricolour.ca> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Richard Guy Briggs Cc: security@kernel.org, Pengfei Wang , "Krinke, Jens" , linux-audit@redhat.com List-Id: linux-audit@redhat.com Not that I understand this report, but On 06/20, Richard Guy Briggs wrote: > > This function is only ever called by __audit_free(), which is only ever > called on failure of task creation or on exit of the task, so in neither > case can anything else change it. How so? Another thread or CLONE_VM task or /proc/pid/mem can change the user-space memory in parallel. Oleg.