linux-kernel - Re: crash by cdc_acm driver in kernels 4.8-rc1/5

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <75DD0AB6-57EB-46F4-B608-4E73EACA4562@mork.no>
Date:   Wed, 23 Nov 2016 08:37:17 +0100
From:   Bjørn Mork <bjorn@...k.no>
To:     wim@....tudelft.nl
CC:     Oliver Neukum <oneukum@...e.com>,
        poma <pomidorabelisima@...il.com>, linux-kernel@...r.kernel.org,
        linux-usb@...r.kernel.org
Subject: Re: crash by cdc_acm driver in kernels 4.8-rc1/5



On November 23, 2016 1:54:57 AM CET, Wim Osterholt <wim@....tudelft.nl> wrote:
>On Tue, Nov 22, 2016 at 07:08:30PM +0100, Bjørn Mork wrote:
>> > On kernel 4.8.8  this crashes hard and produces over a serial link:
>> 
>> Huh?  That device shouldn't ever enter that code path AFAICS.
>> Unless.... you wouldn't happen to add a dynamic entry for this
>device,
>
>No idea of what you mean here.
>
>> would you?  What's the output of
>> 
>>  cat /sys/bus/usb/drivers/cdc_acm/new_id
>
>Just empty.

Shit. Back to not understanding how you could possibly enter the debugging code at all.

Bjørn