<?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://vulnerability.circl.lu</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, 29 Sep 2026 15:58:08 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50453 — gpiolib: cdev: fix NULL-pointer dereferences</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-50453</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;gpiolib: cdev: fix NULL-pointer dereferences&lt;/p&gt;
&lt;p&gt;There are several places where we can crash the kernel by requesting
lines, unbinding the GPIO device, then calling any of the system calls
relevant to the GPIO character device&amp;#39;s annonymous file descriptors:
ioctl(), read(), poll().&lt;/p&gt;
&lt;p&gt;While I observed it with the GPIO simulator, it will also happen for any
of the GPIO devices that can be hot-unplugged - for instance any HID GPIO
expander (e.g. CP2112).&lt;/p&gt;
&lt;p&gt;This affects both v1 and v2 uAPI.&lt;/p&gt;
&lt;p&gt;This fixes it partially by checking if gdev-&amp;gt;chip is not NULL but it
doesn&amp;#39;t entirely remedy the situation as we still have a race condition
in which another thread can remove the device after the check.&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;gpiolib: cdev: fix NULL-pointer dereferences&lt;/p&gt;
&lt;p&gt;There are several places where we can crash the kernel by requesting
lines, unbinding the GPIO device, then calling any of the system calls
relevant to the GPIO character device&amp;#39;s annonymous file descriptors:
ioctl(), read(), poll().&lt;/p&gt;
&lt;p&gt;While I observed it with the GPIO simulator, it will also happen for any
of the GPIO devices that can be hot-unplugged - for instance any HID GPIO
expander (e.g. CP2112).&lt;/p&gt;
&lt;p&gt;This affects both v1 and v2 uAPI.&lt;/p&gt;
&lt;p&gt;This fixes it partially by checking if gdev-&amp;gt;chip is not NULL but it
doesn&amp;#39;t entirely remedy the situation as we still have a race condition
in which another thread can remove the device after the check.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-50453</guid>
    </item>
  </channel>
</rss>
