<?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>Thu, 01 Oct 2026 02:56:32 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64027 — net: shaper: rework the VALID marking (again)</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64027</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;net: shaper: rework the VALID marking (again)&lt;/p&gt;
&lt;p&gt;Recent commit changed the semantics from NOT_VALID to VALID.
I didn&amp;#39;t realize that the flags are not stored atomically
with the entry in XArray. There&amp;#39;s still a race of reader
observing a VALID mark for a slot, getting interrupted,
writer replacing the entry with a different one, reader
continuing, fetching the entry which is now a different
pointer than the pointer for which VALID was meant.&lt;/p&gt;
&lt;p&gt;The biggest consequence of this is that we may see a UAF
since net_shaper_rollback() assumed that entries without
VALID can be freed without observing RCU.&lt;/p&gt;
&lt;p&gt;Looks like the XArray marks are buying us nothing at this
point. Let&amp;#39;s convert the code to an explicit valid field.
The smp_load_acquire() / smp_store_release() barriers are
marginally cleaner.&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;net: shaper: rework the VALID marking (again)&lt;/p&gt;
&lt;p&gt;Recent commit changed the semantics from NOT_VALID to VALID.
I didn&amp;#39;t realize that the flags are not stored atomically
with the entry in XArray. There&amp;#39;s still a race of reader
observing a VALID mark for a slot, getting interrupted,
writer replacing the entry with a different one, reader
continuing, fetching the entry which is now a different
pointer than the pointer for which VALID was meant.&lt;/p&gt;
&lt;p&gt;The biggest consequence of this is that we may see a UAF
since net_shaper_rollback() assumed that entries without
VALID can be freed without observing RCU.&lt;/p&gt;
&lt;p&gt;Looks like the XArray marks are buying us nothing at this
point. Let&amp;#39;s convert the code to an explicit valid field.
The smp_load_acquire() / smp_store_release() barriers are
marginally cleaner.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64027</guid>
    </item>
  </channel>
</rss>
