<?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:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68426 — xfrm: fix stale skb-&gt;prev after async crypto steals a GSO segment</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68426</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;xfrm: fix stale skb-&amp;gt;prev after async crypto steals a GSO segment&lt;/p&gt;
&lt;p&gt;skb_gso_segment() leaves the segment list head with -&amp;gt;prev pointing at
the last segment, an invariant validate_xmit_skb_list() relies on when
it sets its tail pointer (tail = skb-&amp;gt;prev).&lt;/p&gt;
&lt;p&gt;When validate_xmit_xfrm() walks a GSO list and some segments are stolen
by async crypto (-&amp;gt;xmit() returns -EINPROGRESS), those segments are
unlinked from the list but the head -&amp;gt;prev is never updated.  If the
last segment is the one stolen, the returned head still has -&amp;gt;prev
pointing at it, even though it is now owned by the crypto engine and may
be freed.  validate_xmit_skb_list() later does tail-&amp;gt;next = skb, writing
through that stale pointer -- a use-after-free.&lt;/p&gt;
&lt;p&gt;Repoint skb-&amp;gt;prev at the last retained segment before returning.&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;xfrm: fix stale skb-&amp;gt;prev after async crypto steals a GSO segment&lt;/p&gt;
&lt;p&gt;skb_gso_segment() leaves the segment list head with -&amp;gt;prev pointing at
the last segment, an invariant validate_xmit_skb_list() relies on when
it sets its tail pointer (tail = skb-&amp;gt;prev).&lt;/p&gt;
&lt;p&gt;When validate_xmit_xfrm() walks a GSO list and some segments are stolen
by async crypto (-&amp;gt;xmit() returns -EINPROGRESS), those segments are
unlinked from the list but the head -&amp;gt;prev is never updated.  If the
last segment is the one stolen, the returned head still has -&amp;gt;prev
pointing at it, even though it is now owned by the crypto engine and may
be freed.  validate_xmit_skb_list() later does tail-&amp;gt;next = skb, writing
through that stale pointer -- a use-after-free.&lt;/p&gt;
&lt;p&gt;Repoint skb-&amp;gt;prev at the last retained segment before returning.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68426</guid>
    </item>
  </channel>
</rss>
