linux-kernel - Re: [PATCH net/next] bridge:Add rcu read lock when delete br port

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: <20140804094822.40a272e3@haswell.linuxnetplumber.net>
Date:	Mon, 4 Aug 2014 09:48:22 -0700
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	<lichunhe@...wei.com>
Cc:	<vyasevic@...hat.com>, <xiyou.wangcong@...il.com>,
	<makita.toshiaki@....ntt.co.jp>, <mst@...hat.com>,
	<ebiederm@...ssion.com>, <f.fainelli@...il.com>,
	<linux-kernel@...r.kernel.org>, <wuyunfei@...wei.com>,
	<qianhuibin@...wei.com>
Subject: Re: [PATCH net/next] bridge:Add rcu read lock when delete br port

On Mon, 4 Aug 2014 11:37:56 +0800
<lichunhe@...wei.com> wrote:

> From: Chunhe Li <lichunhe@...wei.com>
> 
> In the br_hanle_frame function has a bug, when the bridge receive packets
> which go througth the br_handle_frame, get the net_bridge_port pointer "p",
> but don't check NULL pointer to use it. If somebody delete the bridge port
> at the same time, will call a NULL pointer, trigger kernel panic. I see the
> del_nbp comments, call del_nbp should via RCU, but the caller don't do this.
> 
> following steps will make bug happened
> 1.start vm and add the vm interface to a bridge br0,for example,
> brctl addbr br0 tap0
> 
> 2.configuer vm interface and br0 same ip subnet, vm ping br0.
> 
> 3.add and delete the vm interface port for endless loop.
> 
> Signed-off-by: Chunhe Li <lichunhe@...wei.com>

Any possible bridge issues should go netdev@...r.kernel.org

Nobody reads LKML anymore.


--
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/