<?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-10-01T19:38:14.157626+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-80846</id>
    <title>CVE-2026-80846 — xfrm: drop ESP-in-TCP packets with no ingress device</title>
    <updated>2026-10-01T19:38:14.160768+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: drop ESP-in-TCP packets with no ingress device</p>
<p>ESP-in-TCP receives records through the TCP strparser. handle_esp()
restores skb-&gt;dev from the saved skb_iif before passing the packet into
the XFRM input path.</p>
<p>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-&gt;dev to be valid while building the route lookup,
so queued ESP-in-TCP data can dereference a NULL device.</p>
<p>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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-80846"/>
  </entry>
</feed>
