netdev - Re: [PATCH] bridge: bad error handling when adding invalid ether address

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20090325.210154.102979690.davem@davemloft.net>
Date:	Wed, 25 Mar 2009 21:01:54 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	shemminger@...tta.com
Cc:	stig@...tta.com, netdev@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] bridge: bad error handling when adding invalid ether
 address

From: Stephen Hemminger <shemminger@...tta.com>
Date: Wed, 25 Mar 2009 20:57:00 -0700

> This fixes an crash when empty bond device is added to a bridge.
> If an interface with invalid ethernet address (all zero) is added
> to a bridge, then bridge code detects it when setting up the forward
> databas entry. But the error unwind is broken, the bridge port object 
> can get freed twice: once when ref count went to zeo, and once by kfree.
> Since object is never really accessible, just free it.
> 
> Signed-off-by: Stephen Hemminger <shemminger@...tta.com>

Applied, thanks.
--
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