<?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>Wed, 30 Sep 2026 15:50:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31532 — can: raw: fix ro-&gt;uniq use-after-free in raw_rcv()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31532</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;can: raw: fix ro-&amp;gt;uniq use-after-free in raw_rcv()&lt;/p&gt;
&lt;p&gt;raw_release() unregisters raw CAN receive filters via can_rx_unregister(),
but receiver deletion is deferred with call_rcu(). This leaves a window
where raw_rcv() may still be running in an RCU read-side critical section
after raw_release() frees ro-&amp;gt;uniq, leading to a use-after-free of the
percpu uniq storage.&lt;/p&gt;
&lt;p&gt;Move free_percpu(ro-&amp;gt;uniq) out of raw_release() and into a raw-specific
socket destructor. can_rx_unregister() takes an extra reference to the
socket and only drops it from the RCU callback, so freeing uniq from
sk_destruct ensures the percpu area is not released until the relevant
callbacks have drained.&lt;/p&gt;
&lt;p&gt;[mkl: applied manually]&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;can: raw: fix ro-&amp;gt;uniq use-after-free in raw_rcv()&lt;/p&gt;
&lt;p&gt;raw_release() unregisters raw CAN receive filters via can_rx_unregister(),
but receiver deletion is deferred with call_rcu(). This leaves a window
where raw_rcv() may still be running in an RCU read-side critical section
after raw_release() frees ro-&amp;gt;uniq, leading to a use-after-free of the
percpu uniq storage.&lt;/p&gt;
&lt;p&gt;Move free_percpu(ro-&amp;gt;uniq) out of raw_release() and into a raw-specific
socket destructor. can_rx_unregister() takes an extra reference to the
socket and only drops it from the RCU callback, so freeing uniq from
sk_destruct ensures the percpu area is not released until the relevant
callbacks have drained.&lt;/p&gt;
&lt;p&gt;[mkl: applied manually]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31532</guid>
    </item>
  </channel>
</rss>
