linux-ext4 - Re: [PATCH] fs/ext3: set pointer = NULL, after kfree it

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]

Date:	Tue, 25 Dec 2012 13:51:55 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	Chen Gang <gang.chen@...anux.com>
Cc:	jack@...e.cz, akpm@...ux-foundation.org, linux-ext4@...r.kernel.org
Subject: Re: [PATCH] fs/ext3: set pointer = NULL, after kfree it

On Mon, Dec 24, 2012 at 01:58:14PM +0800, Chen Gang wrote:
> 
>   set s->base = NULL, after kfree it.
> 
> Signed-off-by: Chen Gang <gang.chen@...anux.com>

Was this to fix something flagged by some static code checker?  The
only caller of ext3_xattr_block_set() is ext3_xattr_set_handle(), and
s->base is stored on the stack, and as soon as ext3_xattr_block_set()
returns, the object will disappear.  So it seems pretty hard to see
how this could lead to a use-after-free bug.

    	       	       	 		- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html