[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170322124548.GC10130@localhost>
Date: Wed, 22 Mar 2017 13:45:48 +0100
From: Johan Hovold <johan@...nel.org>
To: Kalle Valo <kvalo@...eaurora.org>
Cc: Johan Hovold <johan@...nel.org>,
QCA ath9k Development <ath9k-devel@....qualcomm.com>,
Daniel Drake <dsd@...too.org>,
Ulrich Kunitz <kune@...ne-taler.de>,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [2/2] zd1211rw: fix NULL-deref at probe
On Wed, Mar 22, 2017 at 09:04:15AM +0000, Kalle Valo wrote:
> Johan Hovold <johan@...nel.org> wrote:
> > Make sure to check the number of endpoints to avoid dereferencing a
> > NULL-pointer or accessing memory beyond the endpoint array should a
> > malicious device lack the expected endpoints.
> >
> > Fixes: a1030e92c150 ("[PATCH] zd1211rw: Convert installer CDROM device into WLAN device")
> > Cc: Daniel Drake <dsd@...too.org>
> > Signed-off-by: Johan Hovold <johan@...nel.org>
>
> Patch applied to wireless-drivers-next.git, thanks.
>
> ca260ece6a57 zd1211rw: fix NULL-deref at probe
What about patch 1/2 which fixes the same bug (literally copied from the
zd1211rw driver)?
And as these fixes should be backported to stable (I left out the tag
for networking drivers), why only apply to -next?
Thanks,
Johan
Powered by blists - more mailing lists