linux-kernel - Re: [PATCH 1/2] fuse: do not use iocb after it may have been freed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160314135421.GO8655@tucsk>
Date:	Mon, 14 Mar 2016 14:54:21 +0100
From:	Miklos Szeredi <miklos@...redi.hu>
To:	Seth Forshee <seth.forshee@...onical.com>
Cc:	m.loschwitz@...eleven.de, robert@...byte.com,
	fuse-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] fuse: do not use iocb after it may have been freed

On Fri, Mar 11, 2016 at 10:35:33AM -0600, Seth Forshee wrote:
> From: Robert Doebbelin <robert@...byte.com>
> 
> Reading wrong data may cause the IO thread to starve waiting for completion.
> The issue was introduced with commit 04b2fa9 and thus affects kernel >= 4.1. It
> was discovered by KASan:

Thanks, queued.

Miklos