<?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>Sun, 04 Oct 2026 21:03:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72463 — xfrm: Fix dev use-after-free in xfrm async resumption</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72463</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 dev use-after-free in xfrm async resumption&lt;/p&gt;
&lt;p&gt;xfrm async resumption hold skb-&amp;gt;dev refcnt until after transport_finish.
However, xfrm_rcv_cb may modify skb-&amp;gt;dev to tunnel dev without taking
device reference, such as vti_rcv_cb. The subsequent async resumption
will decrement the tunnel device&amp;#39;s reference count, which lead to uaf
of tunnel dev and refcnt leak of orig dev as below:&lt;/p&gt;
&lt;p&gt;unregister_netdevice: waiting for vti1 to become free. Usage count = -2&lt;/p&gt;
&lt;p&gt;Stash the original skb-&amp;gt;dev to fix refcnt imbalance. The new skb-&amp;gt;dev set
by xfrm_rcv_cb can race with device teardown. Extend rcu protection over
xfrm_rcv_cb and transport_finish to prevent races.&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 dev use-after-free in xfrm async resumption&lt;/p&gt;
&lt;p&gt;xfrm async resumption hold skb-&amp;gt;dev refcnt until after transport_finish.
However, xfrm_rcv_cb may modify skb-&amp;gt;dev to tunnel dev without taking
device reference, such as vti_rcv_cb. The subsequent async resumption
will decrement the tunnel device&amp;#39;s reference count, which lead to uaf
of tunnel dev and refcnt leak of orig dev as below:&lt;/p&gt;
&lt;p&gt;unregister_netdevice: waiting for vti1 to become free. Usage count = -2&lt;/p&gt;
&lt;p&gt;Stash the original skb-&amp;gt;dev to fix refcnt imbalance. The new skb-&amp;gt;dev set
by xfrm_rcv_cb can race with device teardown. Extend rcu protection over
xfrm_rcv_cb and transport_finish to prevent races.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72463</guid>
    </item>
  </channel>
</rss>
