<?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-01T03:16:47.021775+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-80612</id>
    <title>CVE-2026-80612 — net: lwtunnel: Drop skb metadata before LWT encapsulation</title>
    <updated>2026-10-01T03:16:48.084987+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>net: lwtunnel: Drop skb metadata before LWT encapsulation</p>
<p>skb metadata is meant for passing information between XDP and TC. It lives
in the skb headroom, immediately before skb-&gt;data. LWT programs cannot
access the __sk_buff-&gt;data_meta pseudo-pointer to metadata.</p>
<p>However, LWT encapsulation prepends outer headers, moving skb-&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:</p>
<p>1. Non-BPF LWT encaps (mpls, seg6, ioam6 ...) call skb_push()/skb_pull()
   and silently overwrite the metadata that sits in the headroom.</p>
<p>2) BPF LWT xmit calls bpf_skb_change_head(), which uses skb_data_move().
   That helper expects metadata immediately before skb-&gt;data. But since
   the IP output path runs LWT xmit before neighbour output has built
   the outgoing L2 header, for forwarded packets skb-&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-&gt;data, warns and clears metadata:</p>
<p>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:
   &lt;IRQ&gt;
   bpf_skb_change_head+0xe6/0x1a0
   bpf_prog_...+0x213/0x…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-80612"/>
  </entry>
</feed>
