<?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>Wed, 30 Sep 2026 23:49:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80612 — net: lwtunnel: Drop skb metadata before LWT encapsulation</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80612</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;net: lwtunnel: Drop skb metadata before LWT encapsulation&lt;/p&gt;
&lt;p&gt;skb metadata is meant for passing information between XDP and TC. It lives
in the skb headroom, immediately before skb-&amp;gt;data. LWT programs cannot
access the __sk_buff-&amp;gt;data_meta pseudo-pointer to metadata.&lt;/p&gt;
&lt;p&gt;However, LWT encapsulation prepends outer headers, moving skb-&amp;gt;data back
over the headroom where the metadata sits. On an RX-originated (forwarded)
packet that still carries XDP metadata this goes wrong in two different
ways, depending on the encap type:&lt;/p&gt;
&lt;p&gt;1. Non-BPF LWT encaps (mpls, seg6, ioam6 ...) call skb_push()/skb_pull()
   and silently overwrite the metadata that sits in the headroom.&lt;/p&gt;
&lt;p&gt;2) BPF LWT xmit calls bpf_skb_change_head(), which uses skb_data_move().
   That helper expects metadata immediately before skb-&amp;gt;data. But since
   the IP output path runs LWT xmit before neighbour output has built
   the outgoing L2 header, for forwarded packets skb-&amp;gt;data points at the
   L3 header while skb_mac_header() still points at the old L2 header.
   skb_data_move() sees metadata ending at skb_mac_header(), not before
   skb-&amp;gt;data, warns and clears metadata:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 21 PID: 454557 at include/linux/skbuff.h:4609 skb_data_move+0x47/0x90
  CPU: 21 UID: 0 PID: 454557 Comm: napi/iconduit-g Tainted: G           O        6.18.21 #1
  RIP: 0010:skb_data_move+0x47/0x90
  Call Trace:
   &amp;lt;IRQ&amp;gt;
   bpf_skb_change_head+0xe6/0x1a0
   bpf_prog_...+0x213/0x…&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;net: lwtunnel: Drop skb metadata before LWT encapsulation&lt;/p&gt;
&lt;p&gt;skb metadata is meant for passing information between XDP and TC. It lives
in the skb headroom, immediately before skb-&amp;gt;data. LWT programs cannot
access the __sk_buff-&amp;gt;data_meta pseudo-pointer to metadata.&lt;/p&gt;
&lt;p&gt;However, LWT encapsulation prepends outer headers, moving skb-&amp;gt;data back
over the headroom where the metadata sits. On an RX-originated (forwarded)
packet that still carries XDP metadata this goes wrong in two different
ways, depending on the encap type:&lt;/p&gt;
&lt;p&gt;1. Non-BPF LWT encaps (mpls, seg6, ioam6 ...) call skb_push()/skb_pull()
   and silently overwrite the metadata that sits in the headroom.&lt;/p&gt;
&lt;p&gt;2) BPF LWT xmit calls bpf_skb_change_head(), which uses skb_data_move().
   That helper expects metadata immediately before skb-&amp;gt;data. But since
   the IP output path runs LWT xmit before neighbour output has built
   the outgoing L2 header, for forwarded packets skb-&amp;gt;data points at the
   L3 header while skb_mac_header() still points at the old L2 header.
   skb_data_move() sees metadata ending at skb_mac_header(), not before
   skb-&amp;gt;data, warns and clears metadata:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 21 PID: 454557 at include/linux/skbuff.h:4609 skb_data_move+0x47/0x90
  CPU: 21 UID: 0 PID: 454557 Comm: napi/iconduit-g Tainted: G           O        6.18.21 #1
  RIP: 0010:skb_data_move+0x47/0x90
  Call Trace:
   &amp;lt;IRQ&amp;gt;
   bpf_skb_change_head+0xe6/0x1a0
   bpf_prog_...+0x213/0x…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80612</guid>
    </item>
  </channel>
</rss>
