linux-kernel - Re: [PATCH] staging: slicoss: fix use-after-free in slic_entry

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: <20140523111454.GA3992@kroah.com>
Date:	Fri, 23 May 2014 20:14:54 +0900
From:	Greg KH <gregkh@...uxfoundation.org>
To:	David Matlack <matlackdavid@...il.com>
Cc:	devel@...verdev.osuosl.org, charrer@...critech.com,
	linux-kernel@...r.kernel.org, liodot@...il.com
Subject: Re: [PATCH] staging: slicoss: fix use-after-free in slic_entry_probe

On Thu, May 22, 2014 at 09:25:40PM -0700, David Matlack wrote:
> Fix a use-after-free bug that can cause a kernel oops. If
> slic_card_init fails then slic_entry_probe() (the pci probe()
> function for this device) will return error without cleaning
> up memory (including the registered netdev struct).
> 
> Signed-off-by: David Matlack <matlackdavid@...il.com>
> ---
> This patch was originally sent here https://lkml.org/lkml/2014/5/6/10 with
> my google.com email address. But due to Google's recent change in DMARC
> policies, that patchset was silently dropped for at least some users
> (including my personal gmail account). So I'm sending it out now with
> my gmail.com account. Let me know if this is an issue. Thanks.

I think I've already applied all of these, if not, please let me know.

Also, you forgot to number these patches to let me know what order to
apply them in :(

thanks,

greg k-h
--
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/