<?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://cve.radiocsirt.org</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 01:52:22 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2026-80612 — CVE-2026-80612 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-80612</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-80612</guid>
    </item>
    <item>
      <title>EUVD-2026-361535</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-361535</link>
      <description>EUVD-2026-361535</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-361535</guid>
    </item>
    <item>
      <title>fkie_cve-2026-80612</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-80612</link>
      <description>&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;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://cve.radiocsirt.org/vuln/fkie_cve-2026-80612</guid>
    </item>
    <item>
      <title>GHSA-gcxj-phfp-fv28</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-gcxj-phfp-fv28</link>
      <description>&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;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://cve.radiocsirt.org/vuln/ghsa-gcxj-phfp-fv28</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-80612</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80612</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 117 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: lwtunnel: Drop skb metadata before LWT encapsulation 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. 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: 1. Non-BPF LWT encaps (mpls, seg6, ioam6 ...) call skb_push()/skb_pull()    and silently overwrite the metadata that sits in the headroom. 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:   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/0x2e3    r…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 117 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: lwtunnel: Drop skb metadata before LWT encapsulation 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. 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: 1. Non-BPF LWT encaps (mpls, seg6, ioam6 ...) call skb_push()/skb_pull()    and silently overwrite the metadata that sits in the headroom. 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:   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/0x2e3    r…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80612</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3075 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3075</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise Speicherbeschädigungen, die Offenlegung oder Manipulation von Daten sowie Denial-of-Service-Zustände.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise Speicherbeschädigungen, die Offenlegung oder Manipulation von Daten sowie Denial-of-Service-Zustände.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3075</guid>
    </item>
  </channel>
</rss>
