<?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>Fri, 02 Oct 2026 17:38:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72489 — staging: nvec: fix use-after-free in nvec_rx_completed()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72489</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;staging: nvec: fix use-after-free in nvec_rx_completed()&lt;/p&gt;
&lt;p&gt;In nvec_rx_completed(), when an incomplete RX transfer is detected,
nvec_msg_free() is called to return the message back to the pool by
clearing its &amp;#39;used&amp;#39; atomic flag. Immediately after this, the code
accesses nvec-&amp;gt;rx-&amp;gt;data[0] to check the message type.&lt;/p&gt;
&lt;p&gt;Since nvec_msg_free() marks the pool slot as available via atomic_set(),
any concurrent or subsequent call to nvec_msg_alloc() could claim that
same slot and overwrite its data[] array. Reading nvec-&amp;gt;rx-&amp;gt;data[0] after
freeing the message is therefore a use-after-free.&lt;/p&gt;
&lt;p&gt;Fix this by saving the message type byte before calling nvec_msg_free(),
then using the saved value for the battery quirk 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;staging: nvec: fix use-after-free in nvec_rx_completed()&lt;/p&gt;
&lt;p&gt;In nvec_rx_completed(), when an incomplete RX transfer is detected,
nvec_msg_free() is called to return the message back to the pool by
clearing its &amp;#39;used&amp;#39; atomic flag. Immediately after this, the code
accesses nvec-&amp;gt;rx-&amp;gt;data[0] to check the message type.&lt;/p&gt;
&lt;p&gt;Since nvec_msg_free() marks the pool slot as available via atomic_set(),
any concurrent or subsequent call to nvec_msg_alloc() could claim that
same slot and overwrite its data[] array. Reading nvec-&amp;gt;rx-&amp;gt;data[0] after
freeing the message is therefore a use-after-free.&lt;/p&gt;
&lt;p&gt;Fix this by saving the message type byte before calling nvec_msg_free(),
then using the saved value for the battery quirk check.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72489</guid>
    </item>
  </channel>
</rss>
