<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 17:09:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50542 — media: si470x: Fix use-after-free in si470x_int_in_callback()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-50542</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: si470x: Fix use-after-free in si470x_int_in_callback()&lt;/p&gt;
&lt;p&gt;syzbot reported use-after-free in si470x_int_in_callback() [1].  This
indicates that urb-&amp;gt;context, which contains struct si470x_device
object, is freed when si470x_int_in_callback() is called.&lt;/p&gt;
&lt;p&gt;The cause of this issue is that si470x_int_in_callback() is called for
freed urb.&lt;/p&gt;
&lt;p&gt;si470x_usb_driver_probe() calls si470x_start_usb(), which then calls
usb_submit_urb() and si470x_start().  If si470x_start_usb() fails,
si470x_usb_driver_probe() doesn&amp;#39;t kill urb, but it just frees struct
si470x_device object, as depicted below:&lt;/p&gt;
&lt;p&gt;si470x_usb_driver_probe()
  ...
  si470x_start_usb()
    ...
    usb_submit_urb()
    retval = si470x_start()
    return retval
  if (retval &amp;lt; 0)
    free struct si470x_device object, but don&amp;#39;t kill urb&lt;/p&gt;
&lt;p&gt;This patch fixes this issue by killing urb when si470x_start_usb()
fails and urb is submitted.  If si470x_start_usb() fails and urb is
not submitted, i.e. submitting usb fails, it just frees struct
si470x_device object.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: si470x: Fix use-after-free in si470x_int_in_callback()&lt;/p&gt;
&lt;p&gt;syzbot reported use-after-free in si470x_int_in_callback() [1].  This
indicates that urb-&amp;gt;context, which contains struct si470x_device
object, is freed when si470x_int_in_callback() is called.&lt;/p&gt;
&lt;p&gt;The cause of this issue is that si470x_int_in_callback() is called for
freed urb.&lt;/p&gt;
&lt;p&gt;si470x_usb_driver_probe() calls si470x_start_usb(), which then calls
usb_submit_urb() and si470x_start().  If si470x_start_usb() fails,
si470x_usb_driver_probe() doesn&amp;#39;t kill urb, but it just frees struct
si470x_device object, as depicted below:&lt;/p&gt;
&lt;p&gt;si470x_usb_driver_probe()
  ...
  si470x_start_usb()
    ...
    usb_submit_urb()
    retval = si470x_start()
    return retval
  if (retval &amp;lt; 0)
    free struct si470x_device object, but don&amp;#39;t kill urb&lt;/p&gt;
&lt;p&gt;This patch fixes this issue by killing urb when si470x_start_usb()
fails and urb is submitted.  If si470x_start_usb() fails and urb is
not submitted, i.e. submitting usb fails, it just frees struct
si470x_device object.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-50542</guid>
    </item>
  </channel>
</rss>
