<?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>Fri, 02 Oct 2026 22:06:58 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-80925</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-80925</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-80925</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1253 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253</link>
      <description>certfr-2026-avi-1253</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253</guid>
    </item>
    <item>
      <title>EUVD-2026-372826</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-372826</link>
      <description>EUVD-2026-372826</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-372826</guid>
    </item>
    <item>
      <title>fkie_cve-2026-80925</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-80925</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vlan: fix skb_under_panic and races when toggling HW VLAN offload&lt;/p&gt;
&lt;p&gt;Toggling hardware VLAN TX offload (NETIF_F_HW_VLAN_CTAG_TX or
NETIF_F_HW_VLAN_STAG_TX) on a lower device invokes vlan_transfer_features(),
which dynamically changed vlandev-&amp;gt;hard_header_len.&lt;/p&gt;
&lt;p&gt;This causes two issues:
1. Lockless TX paths (e.g. packet_snd in af_packet.c, ip6_finish_output2)
   read dev-&amp;gt;hard_header_len without holding RTNL lock. Mutating
   hard_header_len dynamically under RTNL creates a data race where upper
   layers reserve insufficient headroom based on a stale hard_header_len,
   resulting in skb_under_panic when vlan_dev_hard_header() is called.
2. In addition, vlan_transfer_features() updated hard_header_len without
   updating header_ops, causing a mismatch between allocated headroom
   and header creation.&lt;/p&gt;
&lt;p&gt;Always setting dev-&amp;gt;hard_header_len = real_dev-&amp;gt;hard_header_len and
dev-&amp;gt;needed_headroom = real_dev-&amp;gt;needed_headroom + VLAN_HLEN unconditionally
ensures:
- dev-&amp;gt;hard_header_len remains 100% static and immutable at real_dev-&amp;gt;hard_header_len,
  eliminating all dynamic runtime updates and data races on hard_header_len.
- Upper layers allocating skbs via LL_RESERVED_SPACE() will always reserve
  sufficient headroom for software VLAN tag insertion (real_dev-&amp;gt;hard_header_len +
  real_dev-&amp;gt;needed_headroom + VLAN_HLEN).
- vlandev inherits real_dev-&amp;gt;needed_tailroom so underlying trailer/padding/ICV
  requirements are honor…&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;vlan: fix skb_under_panic and races when toggling HW VLAN offload&lt;/p&gt;
&lt;p&gt;Toggling hardware VLAN TX offload (NETIF_F_HW_VLAN_CTAG_TX or
NETIF_F_HW_VLAN_STAG_TX) on a lower device invokes vlan_transfer_features(),
which dynamically changed vlandev-&amp;gt;hard_header_len.&lt;/p&gt;
&lt;p&gt;This causes two issues:
1. Lockless TX paths (e.g. packet_snd in af_packet.c, ip6_finish_output2)
   read dev-&amp;gt;hard_header_len without holding RTNL lock. Mutating
   hard_header_len dynamically under RTNL creates a data race where upper
   layers reserve insufficient headroom based on a stale hard_header_len,
   resulting in skb_under_panic when vlan_dev_hard_header() is called.
2. In addition, vlan_transfer_features() updated hard_header_len without
   updating header_ops, causing a mismatch between allocated headroom
   and header creation.&lt;/p&gt;
&lt;p&gt;Always setting dev-&amp;gt;hard_header_len = real_dev-&amp;gt;hard_header_len and
dev-&amp;gt;needed_headroom = real_dev-&amp;gt;needed_headroom + VLAN_HLEN unconditionally
ensures:
- dev-&amp;gt;hard_header_len remains 100% static and immutable at real_dev-&amp;gt;hard_header_len,
  eliminating all dynamic runtime updates and data races on hard_header_len.
- Upper layers allocating skbs via LL_RESERVED_SPACE() will always reserve
  sufficient headroom for software VLAN tag insertion (real_dev-&amp;gt;hard_header_len +
  real_dev-&amp;gt;needed_headroom + VLAN_HLEN).
- vlandev inherits real_dev-&amp;gt;needed_tailroom so underlying trailer/padding/ICV
  requirements are honor…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-80925</guid>
    </item>
    <item>
      <title>GHSA-rp2g-gfw2-xg88</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rp2g-gfw2-xg88</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vlan: fix skb_under_panic and races when toggling HW VLAN offload&lt;/p&gt;
&lt;p&gt;Toggling hardware VLAN TX offload (NETIF_F_HW_VLAN_CTAG_TX or
NETIF_F_HW_VLAN_STAG_TX) on a lower device invokes vlan_transfer_features(),
which dynamically changed vlandev-&amp;gt;hard_header_len.&lt;/p&gt;
&lt;p&gt;This causes two issues:
1. Lockless TX paths (e.g. packet_snd in af_packet.c, ip6_finish_output2)
   read dev-&amp;gt;hard_header_len without holding RTNL lock. Mutating
   hard_header_len dynamically under RTNL creates a data race where upper
   layers reserve insufficient headroom based on a stale hard_header_len,
   resulting in skb_under_panic when vlan_dev_hard_header() is called.
2. In addition, vlan_transfer_features() updated hard_header_len without
   updating header_ops, causing a mismatch between allocated headroom
   and header creation.&lt;/p&gt;
&lt;p&gt;Always setting dev-&amp;gt;hard_header_len = real_dev-&amp;gt;hard_header_len and
dev-&amp;gt;needed_headroom = real_dev-&amp;gt;needed_headroom + VLAN_HLEN unconditionally
ensures:
- dev-&amp;gt;hard_header_len remains 100% static and immutable at real_dev-&amp;gt;hard_header_len,
  eliminating all dynamic runtime updates and data races on hard_header_len.
- Upper layers allocating skbs via LL_RESERVED_SPACE() will always reserve
  sufficient headroom for software VLAN tag insertion (real_dev-&amp;gt;hard_header_len +
  real_dev-&amp;gt;needed_headroom + VLAN_HLEN).
- vlandev inherits real_dev-&amp;gt;needed_tailroom so underlying trailer/padding/ICV
  requirements are honor…&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;vlan: fix skb_under_panic and races when toggling HW VLAN offload&lt;/p&gt;
&lt;p&gt;Toggling hardware VLAN TX offload (NETIF_F_HW_VLAN_CTAG_TX or
NETIF_F_HW_VLAN_STAG_TX) on a lower device invokes vlan_transfer_features(),
which dynamically changed vlandev-&amp;gt;hard_header_len.&lt;/p&gt;
&lt;p&gt;This causes two issues:
1. Lockless TX paths (e.g. packet_snd in af_packet.c, ip6_finish_output2)
   read dev-&amp;gt;hard_header_len without holding RTNL lock. Mutating
   hard_header_len dynamically under RTNL creates a data race where upper
   layers reserve insufficient headroom based on a stale hard_header_len,
   resulting in skb_under_panic when vlan_dev_hard_header() is called.
2. In addition, vlan_transfer_features() updated hard_header_len without
   updating header_ops, causing a mismatch between allocated headroom
   and header creation.&lt;/p&gt;
&lt;p&gt;Always setting dev-&amp;gt;hard_header_len = real_dev-&amp;gt;hard_header_len and
dev-&amp;gt;needed_headroom = real_dev-&amp;gt;needed_headroom + VLAN_HLEN unconditionally
ensures:
- dev-&amp;gt;hard_header_len remains 100% static and immutable at real_dev-&amp;gt;hard_header_len,
  eliminating all dynamic runtime updates and data races on hard_header_len.
- Upper layers allocating skbs via LL_RESERVED_SPACE() will always reserve
  sufficient headroom for software VLAN tag insertion (real_dev-&amp;gt;hard_header_len +
  real_dev-&amp;gt;needed_headroom + VLAN_HLEN).
- vlandev inherits real_dev-&amp;gt;needed_tailroom so underlying trailer/padding/ICV
  requirements are honor…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rp2g-gfw2-xg88</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-80925 — vlan: fix skb_under_panic and races when toggling HW VLAN offload</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-80925</link>
      <description>msrc_CVE-2026-80925</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-80925</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11773-1 — kernel-devel-7.2.5-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11773-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.5-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.5-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11773-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-80925</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80925</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vlan: fix skb_under_panic and races when toggling HW VLAN offload Toggling hardware VLAN TX offload (NETIF_F_HW_VLAN_CTAG_TX or NETIF_F_HW_VLAN_STAG_TX) on a lower device invokes vlan_transfer_features(), which dynamically changed vlandev-&amp;gt;hard_header_len. This causes two issues: 1. Lockless TX paths (e.g. packet_snd in af_packet.c, ip6_finish_output2)    read dev-&amp;gt;hard_header_len without holding RTNL lock. Mutating    hard_header_len dynamically under RTNL creates a data race where upper    layers reserve insufficient headroom based on a stale hard_header_len,    resulting in skb_under_panic when vlan_dev_hard_header() is called. 2. In addition, vlan_transfer_features() updated hard_header_len without    updating header_ops, causing a mismatch between allocated headroom    and header creation. Always setting dev-&amp;gt;hard_header_len = real_dev-&amp;gt;hard_header_len and dev-&amp;gt;needed_headroom = real_dev-&amp;gt;needed_headroom + VLAN_HLEN unconditionally ensures: - dev-&amp;gt;hard_header_len remains 100% static and immutable at real_dev-&amp;gt;hard_header_len,   eliminating all dynamic runtime updates and data races on hard_header_len. - Upper layers allocating skbs via LL_RESERVED_SPACE() will always reserve   sufficient headroom for software VLAN tag insertion (real_dev-&amp;gt;hard_header_len +   real_dev-&amp;gt;needed_headroom + VLAN_HLEN). - vlandev inherits real_dev-&amp;gt;needed_tailroom so underlying trailer/padding/ICV   requirements are honored.…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vlan: fix skb_under_panic and races when toggling HW VLAN offload Toggling hardware VLAN TX offload (NETIF_F_HW_VLAN_CTAG_TX or NETIF_F_HW_VLAN_STAG_TX) on a lower device invokes vlan_transfer_features(), which dynamically changed vlandev-&amp;gt;hard_header_len. This causes two issues: 1. Lockless TX paths (e.g. packet_snd in af_packet.c, ip6_finish_output2)    read dev-&amp;gt;hard_header_len without holding RTNL lock. Mutating    hard_header_len dynamically under RTNL creates a data race where upper    layers reserve insufficient headroom based on a stale hard_header_len,    resulting in skb_under_panic when vlan_dev_hard_header() is called. 2. In addition, vlan_transfer_features() updated hard_header_len without    updating header_ops, causing a mismatch between allocated headroom    and header creation. Always setting dev-&amp;gt;hard_header_len = real_dev-&amp;gt;hard_header_len and dev-&amp;gt;needed_headroom = real_dev-&amp;gt;needed_headroom + VLAN_HLEN unconditionally ensures: - dev-&amp;gt;hard_header_len remains 100% static and immutable at real_dev-&amp;gt;hard_header_len,   eliminating all dynamic runtime updates and data races on hard_header_len. - Upper layers allocating skbs via LL_RESERVED_SPACE() will always reserve   sufficient headroom for software VLAN tag insertion (real_dev-&amp;gt;hard_header_len +   real_dev-&amp;gt;needed_headroom + VLAN_HLEN). - vlandev inherits real_dev-&amp;gt;needed_tailroom so underlying trailer/padding/ICV   requirements are honored.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80925</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3294 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3294</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, sensible Informationen offenzulegen, Daten zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, sensible Informationen offenzulegen, Daten zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3294</guid>
    </item>
  </channel>
</rss>
