[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1509981658.2024.37.camel@suse.com>
Date: Mon, 06 Nov 2017 16:20:58 +0100
From: Oliver Neukum <oneukum@...e.com>
To: Andrey Konovalov <andreyknvl@...gle.com>
Cc: allan <allan@...x.com.tw>,
Colin Ian King <colin.king@...onical.com>,
"David S . Miller" <davem@...emloft.net>,
Philippe Reynes <tremyfr@...il.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Kostya Serebryany <kcc@...gle.com>,
Greg Ungerer <gerg@...ux-m68k.org>,
Dean Jenkins <Dean_Jenkins@...tor.com>,
Peter Chen <peter.chen@....com>,
LKML <linux-kernel@...r.kernel.org>,
USB list <linux-usb@...r.kernel.org>,
netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH] net: usb: asix: fill null-ptr-deref in asix_suspend
Am Montag, den 06.11.2017, 13:30 +0100 schrieb Andrey Konovalov:
> On Mon, Nov 6, 2017 at 10:49 AM, Oliver Neukum <oneukum@...e.com> wrote:
> >
> >
> > 2. Will a device work after that? The appropriate fix may be to wait
> > until the device is properly initialized.
>
> This shouldn't affect real devices as far as I understand. The crash
> can be caused by a crafted malicious device.
Hi!
Hm. That seems strange as driver_priv is kmalloced. Do you
still have a descriptor that causes this?
Shouldn't we rather reject such a broken device?
Regards
Oliver
Powered by blists - more mailing lists