<?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>Tue, 17 Nov 2026 10:10:18 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-99033</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-99033</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-99033</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1537 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537</link>
      <description>certfr-2026-avi-1537</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537</guid>
    </item>
    <item>
      <title>EUVD-2026-396135</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-396135</link>
      <description>EUVD-2026-396135</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-396135</guid>
    </item>
    <item>
      <title>fkie_cve-2026-99033</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99033</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/packet: guard the ll header push in packet_rcv_spkt()&lt;/p&gt;
&lt;p&gt;packet_rcv_spkt() restores the link layer header with&lt;/p&gt;
&lt;p&gt;skb_push(skb, skb-&amp;gt;data - skb_mac_header(skb));&lt;/p&gt;
&lt;p&gt;That subtraction is only meaningful when the device actually has a link
layer header.  packet_rcv() and tpacket_rcv() both wrap it in
dev_has_header(), which is also the predicate the block comment at the
top of the file states the restore in terms of; packet_rcv_spkt() does
not.  commit d549699048b4 (&amp;#34;net/packet: fix packet receive on L3
devices without visible hard header&amp;#34;) introduced the helper and changed
the two call sites, and this one stayed behind.&lt;/p&gt;
&lt;p&gt;A device without a visible ll header can leave skb-&amp;gt;mac_header at the
0xFFFF sentinel that __alloc_skb() initialises it to.  A CAN skb does:
init_can_skb() sets pkt_type and ip_summed but does not reset the
headers, and commit 9f10374bb024 (&amp;#34;can: remove private CAN skb
headroom infrastructure&amp;#34;) dropped the skb_reset_*_header() calls that
used to be there.  skb_mac_header() is then 0xFFFF, the length becomes
a large negative number and skb_push() reports it through
skb_under_panic() -- from softirq context, so it is a full system panic
even with panic_on_oops=0:&lt;/p&gt;
&lt;p&gt;skbuff: skb_under_panic: text:ffffffff8bd21bc1 len:-65455 put:-65471 head:... data:... tail:0x50 end:0x180 dev:can0
  kernel BUG at net/core/skbuff.c:214!
  RIP: 0010:skb_panic+0x50/0x60
  Call Trace:
   &amp;lt;IRQ&amp;gt;
   skb_push+0x38/0x40…&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/packet: guard the ll header push in packet_rcv_spkt()&lt;/p&gt;
&lt;p&gt;packet_rcv_spkt() restores the link layer header with&lt;/p&gt;
&lt;p&gt;skb_push(skb, skb-&amp;gt;data - skb_mac_header(skb));&lt;/p&gt;
&lt;p&gt;That subtraction is only meaningful when the device actually has a link
layer header.  packet_rcv() and tpacket_rcv() both wrap it in
dev_has_header(), which is also the predicate the block comment at the
top of the file states the restore in terms of; packet_rcv_spkt() does
not.  commit d549699048b4 (&amp;#34;net/packet: fix packet receive on L3
devices without visible hard header&amp;#34;) introduced the helper and changed
the two call sites, and this one stayed behind.&lt;/p&gt;
&lt;p&gt;A device without a visible ll header can leave skb-&amp;gt;mac_header at the
0xFFFF sentinel that __alloc_skb() initialises it to.  A CAN skb does:
init_can_skb() sets pkt_type and ip_summed but does not reset the
headers, and commit 9f10374bb024 (&amp;#34;can: remove private CAN skb
headroom infrastructure&amp;#34;) dropped the skb_reset_*_header() calls that
used to be there.  skb_mac_header() is then 0xFFFF, the length becomes
a large negative number and skb_push() reports it through
skb_under_panic() -- from softirq context, so it is a full system panic
even with panic_on_oops=0:&lt;/p&gt;
&lt;p&gt;skbuff: skb_under_panic: text:ffffffff8bd21bc1 len:-65455 put:-65471 head:... data:... tail:0x50 end:0x180 dev:can0
  kernel BUG at net/core/skbuff.c:214!
  RIP: 0010:skb_panic+0x50/0x60
  Call Trace:
   &amp;lt;IRQ&amp;gt;
   skb_push+0x38/0x40…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-99033</guid>
    </item>
    <item>
      <title>GHSA-4crx-j28m-6wrf</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4crx-j28m-6wrf</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/packet: guard the ll header push in packet_rcv_spkt()&lt;/p&gt;
&lt;p&gt;packet_rcv_spkt() restores the link layer header with&lt;/p&gt;
&lt;p&gt;skb_push(skb, skb-&amp;gt;data - skb_mac_header(skb));&lt;/p&gt;
&lt;p&gt;That subtraction is only meaningful when the device actually has a link
layer header.  packet_rcv() and tpacket_rcv() both wrap it in
dev_has_header(), which is also the predicate the block comment at the
top of the file states the restore in terms of; packet_rcv_spkt() does
not.  commit d549699048b4 (&amp;#34;net/packet: fix packet receive on L3
devices without visible hard header&amp;#34;) introduced the helper and changed
the two call sites, and this one stayed behind.&lt;/p&gt;
&lt;p&gt;A device without a visible ll header can leave skb-&amp;gt;mac_header at the
0xFFFF sentinel that __alloc_skb() initialises it to.  A CAN skb does:
init_can_skb() sets pkt_type and ip_summed but does not reset the
headers, and commit 9f10374bb024 (&amp;#34;can: remove private CAN skb
headroom infrastructure&amp;#34;) dropped the skb_reset_*_header() calls that
used to be there.  skb_mac_header() is then 0xFFFF, the length becomes
a large negative number and skb_push() reports it through
skb_under_panic() -- from softirq context, so it is a full system panic
even with panic_on_oops=0:&lt;/p&gt;
&lt;p&gt;skbuff: skb_under_panic: text:ffffffff8bd21bc1 len:-65455 put:-65471 head:... data:... tail:0x50 end:0x180 dev:can0
  kernel BUG at net/core/skbuff.c:214!
  RIP: 0010:skb_panic+0x50/0x60
  Call Trace:
   &amp;lt;IRQ&amp;gt;
   skb_push+0x38/0x40…&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/packet: guard the ll header push in packet_rcv_spkt()&lt;/p&gt;
&lt;p&gt;packet_rcv_spkt() restores the link layer header with&lt;/p&gt;
&lt;p&gt;skb_push(skb, skb-&amp;gt;data - skb_mac_header(skb));&lt;/p&gt;
&lt;p&gt;That subtraction is only meaningful when the device actually has a link
layer header.  packet_rcv() and tpacket_rcv() both wrap it in
dev_has_header(), which is also the predicate the block comment at the
top of the file states the restore in terms of; packet_rcv_spkt() does
not.  commit d549699048b4 (&amp;#34;net/packet: fix packet receive on L3
devices without visible hard header&amp;#34;) introduced the helper and changed
the two call sites, and this one stayed behind.&lt;/p&gt;
&lt;p&gt;A device without a visible ll header can leave skb-&amp;gt;mac_header at the
0xFFFF sentinel that __alloc_skb() initialises it to.  A CAN skb does:
init_can_skb() sets pkt_type and ip_summed but does not reset the
headers, and commit 9f10374bb024 (&amp;#34;can: remove private CAN skb
headroom infrastructure&amp;#34;) dropped the skb_reset_*_header() calls that
used to be there.  skb_mac_header() is then 0xFFFF, the length becomes
a large negative number and skb_push() reports it through
skb_under_panic() -- from softirq context, so it is a full system panic
even with panic_on_oops=0:&lt;/p&gt;
&lt;p&gt;skbuff: skb_under_panic: text:ffffffff8bd21bc1 len:-65455 put:-65471 head:... data:... tail:0x50 end:0x180 dev:can0
  kernel BUG at net/core/skbuff.c:214!
  RIP: 0010:skb_panic+0x50/0x60
  Call Trace:
   &amp;lt;IRQ&amp;gt;
   skb_push+0x38/0x40…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4crx-j28m-6wrf</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99033 — net/packet: guard the ll header push in packet_rcv_spkt()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99033</link>
      <description>msrc_CVE-2026-99033</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-99033</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99033</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99033</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 203 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/packet: guard the ll header push in packet_rcv_spkt() packet_rcv_spkt() restores the link layer header with 	skb_push(skb, skb-&amp;gt;data - skb_mac_header(skb)); That subtraction is only meaningful when the device actually has a link layer header.  packet_rcv() and tpacket_rcv() both wrap it in dev_has_header(), which is also the predicate the block comment at the top of the file states the restore in terms of; packet_rcv_spkt() does not.  commit d549699048b4 (&amp;#34;net/packet: fix packet receive on L3 devices without visible hard header&amp;#34;) introduced the helper and changed the two call sites, and this one stayed behind. A device without a visible ll header can leave skb-&amp;gt;mac_header at the 0xFFFF sentinel that __alloc_skb() initialises it to.  A CAN skb does: init_can_skb() sets pkt_type and ip_summed but does not reset the headers, and commit 9f10374bb024 (&amp;#34;can: remove private CAN skb headroom infrastructure&amp;#34;) dropped the skb_reset_*_header() calls that used to be there.  skb_mac_header() is then 0xFFFF, the length becomes a large negative number and skb_push() reports it through skb_under_panic() -- from softirq context, so it is a full system panic even with panic_on_oops=0:   skbuff: skb_under_panic: text:ffffffff8bd21bc1 len:-65455 put:-65471 head:... data:... tail:0x50 end:0x180 dev:can0   kernel BUG at net/core/skbuff.c:214!   RIP: 0010:skb_panic+0x50/0x60   Call Trace:    &amp;lt;IRQ&amp;gt;    skb_push+0x38/0x40    pack…&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 203 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/packet: guard the ll header push in packet_rcv_spkt() packet_rcv_spkt() restores the link layer header with 	skb_push(skb, skb-&amp;gt;data - skb_mac_header(skb)); That subtraction is only meaningful when the device actually has a link layer header.  packet_rcv() and tpacket_rcv() both wrap it in dev_has_header(), which is also the predicate the block comment at the top of the file states the restore in terms of; packet_rcv_spkt() does not.  commit d549699048b4 (&amp;#34;net/packet: fix packet receive on L3 devices without visible hard header&amp;#34;) introduced the helper and changed the two call sites, and this one stayed behind. A device without a visible ll header can leave skb-&amp;gt;mac_header at the 0xFFFF sentinel that __alloc_skb() initialises it to.  A CAN skb does: init_can_skb() sets pkt_type and ip_summed but does not reset the headers, and commit 9f10374bb024 (&amp;#34;can: remove private CAN skb headroom infrastructure&amp;#34;) dropped the skb_reset_*_header() calls that used to be there.  skb_mac_header() is then 0xFFFF, the length becomes a large negative number and skb_push() reports it through skb_under_panic() -- from softirq context, so it is a full system panic even with panic_on_oops=0:   skbuff: skb_under_panic: text:ffffffff8bd21bc1 len:-65455 put:-65471 head:... data:... tail:0x50 end:0x180 dev:can0   kernel BUG at net/core/skbuff.c:214!   RIP: 0010:skb_panic+0x50/0x60   Call Trace:    &amp;lt;IRQ&amp;gt;    skb_push+0x38/0x40    pack…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99033</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&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, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</guid>
    </item>
  </channel>
</rss>
