linux-kernel - Re: NULL pointer dereference in mainline and next

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: <20111128.170840.1847881572380941723.davem@davemloft.net>
Date:	Mon, 28 Nov 2011 17:08:40 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	will.deacon@....com
Cc:	eric.dumazet@...il.com, mmaruseac@...acom.com,
	linux-kernel@...r.kernel.org
Subject: Re: NULL pointer dereference in mainline and next

From: Will Deacon <will.deacon@....com>
Date: Mon, 28 Nov 2011 14:35:58 +0000

> On Mon, Nov 28, 2011 at 02:33:24PM +0000, Eric Dumazet wrote:
>> Le lundi 28 novembre 2011 à 14:18 +0000, Will Deacon a écrit :
>> > Hello,
>> > 
>> > Commit f04565dd ("dev: use name hash for dev_seq_ops") requires a struct
>> > dev_iter_state to be allocated for the seq_file->private member, as that is
>> > used to implement the name hash.
>> > 
>> > Unfortunately, the dev_mcast code wasn't updated and so only allocates space
>> > for a seq_net_private, leading to the following NULL dereference (removed
>> > static inline annotations to get sane backtrace):
> 
> [...]
> 
>> Anton Blanchard already provided a fix for this problem.
>> 
>> http://patchwork.ozlabs.org/patch/127931/
> 
> Ok, great - as long as it gets fixed!

Please in the future report networking bugs to netdev@...r.kernel.org as that
will reach the largest number of networking developers.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/