<?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>Sat, 03 Oct 2026 22:39:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64238 — gpio: shared: fix deadlock on shared proxy's parent removal</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64238</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;gpio: shared: fix deadlock on shared proxy&amp;#39;s parent removal&lt;/p&gt;
&lt;p&gt;Commit 710abda58055 (&amp;#34;gpio: shared: call gpio_chip::of_xlate() if set&amp;#34;)
used the mutex embedded in struct gpio_shared_entry to protect the
offset field which now can be modified after assignment. The critical
section however is too wide and introduced a potential deadlock on the
removal of the shared GPIO proxy&amp;#39;s parent.&lt;/p&gt;
&lt;p&gt;Make the critical section shorter - only protect the offset when it&amp;#39;s
being read.&lt;/p&gt;
&lt;p&gt;While at it: mention the fact that the entry lock is now also used to
protect against concurrent access to the offset field in the structure&amp;#39;s
documentation.&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;gpio: shared: fix deadlock on shared proxy&amp;#39;s parent removal&lt;/p&gt;
&lt;p&gt;Commit 710abda58055 (&amp;#34;gpio: shared: call gpio_chip::of_xlate() if set&amp;#34;)
used the mutex embedded in struct gpio_shared_entry to protect the
offset field which now can be modified after assignment. The critical
section however is too wide and introduced a potential deadlock on the
removal of the shared GPIO proxy&amp;#39;s parent.&lt;/p&gt;
&lt;p&gt;Make the critical section shorter - only protect the offset when it&amp;#39;s
being read.&lt;/p&gt;
&lt;p&gt;While at it: mention the fact that the entry lock is now also used to
protect against concurrent access to the offset field in the structure&amp;#39;s
documentation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64238</guid>
    </item>
  </channel>
</rss>
