<?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 22:57:40 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80846 — xfrm: drop ESP-in-TCP packets with no ingress device</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80846</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: drop ESP-in-TCP packets with no ingress device&lt;/p&gt;
&lt;p&gt;ESP-in-TCP receives records through the TCP strparser. handle_esp()
restores skb-&amp;gt;dev from the saved skb_iif before passing the packet into
the XFRM input path.&lt;/p&gt;
&lt;p&gt;Queued TCP data can be processed after the original ingress device has
been removed, for example during veth or net namespace teardown. In that
case dev_get_by_index_rcu() returns NULL. The XFRM IPv4 and IPv6 input
paths both expect skb-&amp;gt;dev to be valid while building the route lookup,
so queued ESP-in-TCP data can dereference a NULL device.&lt;/p&gt;
&lt;p&gt;Drop the packet if the saved ingress device can no longer be resolved.
Such a packet can no longer be routed through the normal XFRM receive
path, and this preserves the existing behaviour for packets whose ingress
device still exists.&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: drop ESP-in-TCP packets with no ingress device&lt;/p&gt;
&lt;p&gt;ESP-in-TCP receives records through the TCP strparser. handle_esp()
restores skb-&amp;gt;dev from the saved skb_iif before passing the packet into
the XFRM input path.&lt;/p&gt;
&lt;p&gt;Queued TCP data can be processed after the original ingress device has
been removed, for example during veth or net namespace teardown. In that
case dev_get_by_index_rcu() returns NULL. The XFRM IPv4 and IPv6 input
paths both expect skb-&amp;gt;dev to be valid while building the route lookup,
so queued ESP-in-TCP data can dereference a NULL device.&lt;/p&gt;
&lt;p&gt;Drop the packet if the saved ingress device can no longer be resolved.
Such a packet can no longer be routed through the normal XFRM receive
path, and this preserves the existing behaviour for packets whose ingress
device still exists.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80846</guid>
    </item>
  </channel>
</rss>
