netdev - Re: use after free bug in socket code

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, 07 Jul 2009 08:19:30 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	LW@...O-electronics.de
Cc:	netdev@...r.kernel.org, urs.thuermann@...kswagen.de,
	oliver.hartkopp@...kswagen.de
Subject: Re: use after free bug in socket code

From: Lothar Waßmann <LW@...O-electronics.de>
Date: Tue, 7 Jul 2009 08:59:59 +0200

> To me it seems much more logical to invalidate any references from
> some object 'B' (struct sock) to some object 'A' (struct socket) when
> object 'A' is being released rather than invalidating them when object
> 'B' is being released.

Because B should hold a reference to A in that situation.

If one object refers to another, it should grab and hold a reference
to that object.
--
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