<?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-03T22:39:18.510821+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-2026-64238</id>
    <title>CVE-2026-64238 — gpio: shared: fix deadlock on shared proxy's parent removal</title>
    <updated>2026-10-03T22:39:18.512502+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>gpio: shared: fix deadlock on shared proxy's parent removal</p>
<p>Commit 710abda58055 ("gpio: shared: call gpio_chip::of_xlate() if set")
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's parent.</p>
<p>Make the critical section shorter - only protect the offset when it's
being read.</p>
<p>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's
documentation.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-64238"/>
  </entry>
</feed>
