linux-kernel - [PATCH 0/1] media: uvc_driver: fix USB Camera ref leak denial of service

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>] [day] [month] [year] [list]

Message-ID: <20180526155041.GA4126@spacedout.fries.net>
Date:   Sat, 26 May 2018 10:50:41 -0500
From:   David Fries <David@...es.net>
To:     linux-kernel@...r.kernel.org
Cc:     Guennadi Liakhovetski <g.liakhovetski@....de>,
        Laurent Pinchart <laurent.pinchart@...asonboard.com>,
        Mauro Carvalho Chehab <mchehab@...pensource.com>,
        stable@...r.kernel.org
Subject: [PATCH 0/1] media: uvc_driver: fix USB Camera ref leak denial of
 service

The patch in the following e-mail fixes a reference count bug, it
seems to me that uvc_unregister_video is a good location to release
the final reference, I find it is called once.  It may sound like a
lot to plug and unplug the USB camera 250 some times, but in my case
"disabled by hub (EMI?), re-enabling..." kept unplugging and plugging
in the device until days later it ran out of minors and I lost the
video security feed.

With this patch, now that the device is actually being removed other
problems are showing up.  Specifically the following if the camera is
removed or `rmmod ehci_pci` while an application is getting video from
it.  It doesn't happen if the camera is not in use.  How do I track
that down?

sysfs group 'power' not found for kobject 'event10'
sysfs group 'power' not found for kobject 'input32'
sysfs group 'id' not found for kobject 'input32'
sysfs group 'capabilities' not found for kobject 'input32'
sysfs group 'power' not found for kobject 'media0'

-- 
David Fries <david@...es.net>