linux-kernel - Re: [PATCH] Initialize pointer on request

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: <20110922182048.GB4709@gere.osrc.amd.com>
Date:	Thu, 22 Sep 2011 20:20:48 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Greg KH <gregkh@...e.de>
Cc:	"Lucas C. Villa Real" <lucasvr@...il.com>,
	linux-kernel@...r.kernel.org, Wey-Yi Guya <wey-yi.w.guy@...el.com>,
	Johannes Berg <johannes.berg@...el.com>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Pekka Enberg <penberg@...nel.org>
Subject: Re: [PATCH] Initialize pointer on request_firmware

On Thu, Sep 22, 2011 at 11:03:27AM -0700, Greg KH wrote:
> The patch was in the 2.6.36 kernel, so by nature of that, 3.0 will also
> have it, right?

Ok, a colleague of mine gave me 3.0.4 to stare at - and you're right
the patch is there. So what is still missing is caca9510ff4e5 from
upstream which reroutes the exit path so that firmware_p is NULLed
before returning -EBUSY.

Lucas, can you apply caca9510ff4e5 from upstream and verify it fixes the
issue for ya?

Thanks.

-- 
Regards/Gruss,
Boris.
--
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/