linux-kernel - Re: [stable] [PATCH 0/2] HID: hidraw, fix two NULL pointer dereferences

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: <20101005174200.GB29937@kroah.com>
Date:	Tue, 5 Oct 2010 10:42:00 -0700
From:	Greg KH <greg@...ah.com>
To:	Antonio Ospite <ospite@...denti.unina.it>
Cc:	linux-input@...r.kernel.org, Jiri Kosina <jkosina@...e.cz>,
	linux-kernel@...r.kernel.org, Oliver Neukum <oliver@...kum.name>,
	stable@...nel.org, Alan Ott <alan@...nal11.us>
Subject: Re: [stable] [PATCH 0/2] HID: hidraw, fix two NULL pointer
 dereferences

On Tue, Oct 05, 2010 at 05:20:15PM +0200, Antonio Ospite wrote:
> Hi,
> 
> here are some fixes to hidraw.
> 
> Patches are against 2.6.36-rc6, but they should be ported to other
> maintained stable kernels as well.
> 
> Antonio Ospite (2):
>   HID: hidraw, fix a NULL pointer dereference in hidraw_ioctl
>   HID: hidraw, fix a NULL pointer dereference in hidraw_write
> 
>  drivers/hid/hidraw.c |   11 +++++++++++
>  1 files changed, 11 insertions(+), 0 deletions(-)
> 
> 
> The first one has been sent already but I am resending it with
> stable@...ble@...nel.org in the recipients list.

Please read Documentation/stable_kernel_rules.txt which shows you how to
properly notify the stable developer to pick up the patch (hint, cc:ing
them on the patch is not the correct way, you need to add the mark to
the signed-off-by: area.)

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/