[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <17522697.476689.1576065344710.JavaMail.zimbra@redhat.com>
Date: Wed, 11 Dec 2019 06:55:44 -0500 (EST)
From: Vladis Dronov <vdronov@...hat.com>
To: Johan Hovold <johan@...nel.org>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
linux-input@...r.kernel.org, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org, stable <stable@...r.kernel.org>
Subject: Re: [PATCH 2/7] Input: aiptek: fix endpoint sanity check
A fix for a bug indeed, thank you Johan.
Best regards,
Vladis Dronov | Red Hat, Inc. | The Core Kernel | Senior Software Engineer
----- Original Message -----
> From: "Johan Hovold" <johan@...nel.org>
> To: "Dmitry Torokhov" <dmitry.torokhov@...il.com>
> Cc: linux-input@...r.kernel.org, linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org, "Johan Hovold"
> <johan@...nel.org>, "stable" <stable@...r.kernel.org>, "Vladis Dronov" <vdronov@...hat.com>
> Sent: Tuesday, December 10, 2019 12:37:32 PM
> Subject: [PATCH 2/7] Input: aiptek: fix endpoint sanity check
>
> The driver was checking the number of endpoints of the first alternate
> setting instead of the current one, something which could lead to the
> driver binding to an invalid interface.
>
> This in turn could cause the driver to misbehave or trigger a WARN() in
> usb_submit_urb() that kernels with panic_on_warn set would choke on.
>
> Fixes: 8e20cf2bce12 ("Input: aiptek - fix crash on detecting device without
> endpoints")
> Cc: stable <stable@...r.kernel.org> # 4.4
> Cc: Vladis Dronov <vdronov@...hat.com>
> Signed-off-by: Johan Hovold <johan@...nel.org>
Powered by blists - more mailing lists