From owner-freebsd-security Wed May 31 9:38:56 2000 Delivered-To: freebsd-security@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id 6878737BDE7 for ; Wed, 31 May 2000 09:38:51 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from modemcable009.62-201-24.mtl.mc.videotron.net ([24.201.62.9]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FVF00ASVNEWBJ@falla.videotron.net> for freebsd-security@FreeBSD.ORG; Wed, 31 May 2000 12:35:20 -0400 (EDT) Date: Wed, 31 May 2000 12:36:47 -0400 (EDT) From: Bosko Milekic Subject: Re: Local FreeBSD, OpenBSD, NetBSD, DoS Vulnerability (fwd) In-reply-to: X-Sender: bmilekic@jehovah.technokratis.com To: Mike Silbersack Cc: FreeBSD-SECURITY Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 31 May 2000, Mike Silbersack wrote: > EVERYONE running a 3.4 box is welcome to test the patch. > > Mike "Silby" Silbersack I don't have a 3.4 machine up right now, but you should check to make sure that all callers to m_get and MGET actually check their return values, even if the call goes in with M_WAIT. I remember seeing some places in the code where callers with M_WAIT automatically assumed that they would be getting an mbuf, which probably has to do with the old behavior of mbufs being allocated with malloc(). I think green mentionned this to me, although I remember fixing a few of them with the initial 4.x patch. -- Bosko Milekic bmilekic@technokratis.com WWW: http://www.technokratis.com/ Voice/Mobile: 514.865.7738 * Pager: 514.921.0237 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message