<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T11:04:51.599706+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2024-58079</id>
    <title>CVE-2024-58079 — media: uvcvideo: Fix crash during unbind if gpio unit is in use</title>
    <updated>2026-10-04T11:04:51.618487+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>media: uvcvideo: Fix crash during unbind if gpio unit is in use</p>
<p>We used the wrong device for the device managed functions. We used the
usb device, when we should be using the interface device.</p>
<p>If we unbind the driver from the usb interface, the cleanup functions
are never called. In our case, the IRQ is never disabled.</p>
<p>If an IRQ is triggered, it will try to access memory sections that are
already free, causing an OOPS.</p>
<p>We cannot use the function devm_request_threaded_irq here. The devm_*
clean functions may be called after the main structure is released by
uvc_delete.</p>
<p>Luckily this bug has small impact, as it is only affected by devices
with gpio units and the user has to unbind the device, a disconnect will
not trigger this error.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2024-58079"/>
  </entry>
</feed>
