netdev - Re: [3.19.0-rc4+] rhashtable: BUG kmalloc-2048 (Not tainted): Poison overwritten

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:	Mon, 19 Jan 2015 12:59:28 +0000
From:	Thomas Graf <tgraf@...g.ch>
To:	Ying Xue <ying.xue@...driver.com>
Cc:	"richard.alpe@...csson.com >> Richard Alpe" 
	<richard.alpe@...csson.com>, Netdev <netdev@...r.kernel.org>,
	tipc-discussion@...ts.sourceforge.net
Subject: Re: [3.19.0-rc4+] rhashtable: BUG kmalloc-2048 (Not tainted): Poison
 overwritten

On 01/19/15 at 04:03pm, Ying Xue wrote:
> On 3.19.0-rc4+, I encountered below error with attached test
> case(bind_netlink.c). Please execute the following commands to reproduce
> the error:
> 
> gcc -Wall -o bind_netlink bind_netlink.c
> ./bind_netlink 1000
> 
> By the way, if we run another test case(bind_tipc.c), the similar issue
> will happen on TIPC socket.
> 
> Therefore, it seems that the issue is closely associated with rhashtable
> instead of specific stacks like netlink or tipc.

Looks like a RCU read side critical section was missed. Does the TIPC
poision warning look the same? offset 2048?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html