<?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>Tue, 29 Sep 2026 03:06:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-53250 — xsk: cache csum_start/csum_offset to fix TOCTOU in xsk_skb_metadata()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-53250</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;xsk: cache csum_start/csum_offset to fix TOCTOU in xsk_skb_metadata()&lt;/p&gt;
&lt;p&gt;The TX metadata area resides in the UMEM buffer which is memory-mapped
and concurrently writable by userspace. In xsk_skb_metadata(),
csum_start and csum_offset are read from shared memory for bounds
validation, then read again for skb assignment. A malicious userspace
application can race to overwrite these values between the two reads,
bypassing the bounds check and causing out-of-bounds memory access
during checksum computation in the transmit path.&lt;/p&gt;
&lt;p&gt;Fix this by reading csum_start and csum_offset into local variables
once, then using the local copies for both validation and assignment.&lt;/p&gt;
&lt;p&gt;Note that other metadata fields (flags, launch_time) and the cached
csum fields may be mutually inconsistent due to concurrent userspace
writes, but this is benign: the only security-critical invariant is
that each field&amp;#39;s validated value is the same one used, which local
caching guarantees.&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;xsk: cache csum_start/csum_offset to fix TOCTOU in xsk_skb_metadata()&lt;/p&gt;
&lt;p&gt;The TX metadata area resides in the UMEM buffer which is memory-mapped
and concurrently writable by userspace. In xsk_skb_metadata(),
csum_start and csum_offset are read from shared memory for bounds
validation, then read again for skb assignment. A malicious userspace
application can race to overwrite these values between the two reads,
bypassing the bounds check and causing out-of-bounds memory access
during checksum computation in the transmit path.&lt;/p&gt;
&lt;p&gt;Fix this by reading csum_start and csum_offset into local variables
once, then using the local copies for both validation and assignment.&lt;/p&gt;
&lt;p&gt;Note that other metadata fields (flags, launch_time) and the cached
csum fields may be mutually inconsistent due to concurrent userspace
writes, but this is benign: the only security-critical invariant is
that each field&amp;#39;s validated value is the same one used, which local
caching guarantees.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-53250</guid>
    </item>
  </channel>
</rss>
