<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T13:03:55.529667+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-68426</id>
    <title>CVE-2026-68426 — xfrm: fix stale skb-&gt;prev after async crypto steals a GSO segment</title>
    <updated>2026-09-29T13:03:56.263790+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>xfrm: fix stale skb-&gt;prev after async crypto steals a GSO segment</p>
<p>skb_gso_segment() leaves the segment list head with -&gt;prev pointing at
the last segment, an invariant validate_xmit_skb_list() relies on when
it sets its tail pointer (tail = skb-&gt;prev).</p>
<p>When validate_xmit_xfrm() walks a GSO list and some segments are stolen
by async crypto (-&gt;xmit() returns -EINPROGRESS), those segments are
unlinked from the list but the head -&gt;prev is never updated.  If the
last segment is the one stolen, the returned head still has -&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-&gt;next = skb, writing
through that stale pointer -- a use-after-free.</p>
<p>Repoint skb-&gt;prev at the last retained segment before returning.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-68426"/>
  </entry>
</feed>
