<?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:12:02 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2026-99066 — CVE-2026-99066 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-99066</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-99066</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-391570</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-391570</link>
      <description>EUVD-2026-391570</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-391570</guid>
    </item>
    <item>
      <title>fkie_cve-2026-99066</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99066</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: dev: init_can_skb(): restore skb header initialization&lt;/p&gt;
&lt;p&gt;Commit 9f10374bb024 (&amp;#34;can: remove private CAN skb headroom infrastructure&amp;#34;)
removed the skb_reset_mac_header()/skb_reset_network_header()/
skb_reset_transport_header() calls from init_can_skb(). As a result, RX
skbs from alloc_can_skb() and friends again carry mac_header = 0xFFFF.
When such an skb reaches packet_rcv_spkt() (SOCK_PACKET), the push length
calculation overflows and triggers skb_under_panic -&amp;gt; kernel BUG -&amp;gt; full
machine panic.&lt;/p&gt;
&lt;p&gt;The same issue was originally reported in 2014 on linux-can and fixed by
commit 969439016d2c (&amp;#34;can: add missing initialisations in CAN related
skbuffs&amp;#34;). packet_rcv_spkt() itself has never been hardened: only
packet_rcv() and tpacket_rcv() gained dev_has_header() checks in
commit d549699048b4 (&amp;#34;net/packet: fix packet receive on L3 devices
without visible hard header&amp;#34;).&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;can: dev: init_can_skb(): restore skb header initialization&lt;/p&gt;
&lt;p&gt;Commit 9f10374bb024 (&amp;#34;can: remove private CAN skb headroom infrastructure&amp;#34;)
removed the skb_reset_mac_header()/skb_reset_network_header()/
skb_reset_transport_header() calls from init_can_skb(). As a result, RX
skbs from alloc_can_skb() and friends again carry mac_header = 0xFFFF.
When such an skb reaches packet_rcv_spkt() (SOCK_PACKET), the push length
calculation overflows and triggers skb_under_panic -&amp;gt; kernel BUG -&amp;gt; full
machine panic.&lt;/p&gt;
&lt;p&gt;The same issue was originally reported in 2014 on linux-can and fixed by
commit 969439016d2c (&amp;#34;can: add missing initialisations in CAN related
skbuffs&amp;#34;). packet_rcv_spkt() itself has never been hardened: only
packet_rcv() and tpacket_rcv() gained dev_has_header() checks in
commit d549699048b4 (&amp;#34;net/packet: fix packet receive on L3 devices
without visible hard header&amp;#34;).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-99066</guid>
    </item>
    <item>
      <title>GHSA-4qj9-2gm5-pxqj</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4qj9-2gm5-pxqj</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: dev: init_can_skb(): restore skb header initialization&lt;/p&gt;
&lt;p&gt;Commit 9f10374bb024 (&amp;#34;can: remove private CAN skb headroom infrastructure&amp;#34;)
removed the skb_reset_mac_header()/skb_reset_network_header()/
skb_reset_transport_header() calls from init_can_skb(). As a result, RX
skbs from alloc_can_skb() and friends again carry mac_header = 0xFFFF.
When such an skb reaches packet_rcv_spkt() (SOCK_PACKET), the push length
calculation overflows and triggers skb_under_panic -&amp;gt; kernel BUG -&amp;gt; full
machine panic.&lt;/p&gt;
&lt;p&gt;The same issue was originally reported in 2014 on linux-can and fixed by
commit 969439016d2c (&amp;#34;can: add missing initialisations in CAN related
skbuffs&amp;#34;). packet_rcv_spkt() itself has never been hardened: only
packet_rcv() and tpacket_rcv() gained dev_has_header() checks in
commit d549699048b4 (&amp;#34;net/packet: fix packet receive on L3 devices
without visible hard header&amp;#34;).&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;can: dev: init_can_skb(): restore skb header initialization&lt;/p&gt;
&lt;p&gt;Commit 9f10374bb024 (&amp;#34;can: remove private CAN skb headroom infrastructure&amp;#34;)
removed the skb_reset_mac_header()/skb_reset_network_header()/
skb_reset_transport_header() calls from init_can_skb(). As a result, RX
skbs from alloc_can_skb() and friends again carry mac_header = 0xFFFF.
When such an skb reaches packet_rcv_spkt() (SOCK_PACKET), the push length
calculation overflows and triggers skb_under_panic -&amp;gt; kernel BUG -&amp;gt; full
machine panic.&lt;/p&gt;
&lt;p&gt;The same issue was originally reported in 2014 on linux-can and fixed by
commit 969439016d2c (&amp;#34;can: add missing initialisations in CAN related
skbuffs&amp;#34;). packet_rcv_spkt() itself has never been hardened: only
packet_rcv() and tpacket_rcv() gained dev_has_header() checks in
commit d549699048b4 (&amp;#34;net/packet: fix packet receive on L3 devices
without visible hard header&amp;#34;).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4qj9-2gm5-pxqj</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99066</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99066</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 127 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: can: dev: init_can_skb(): restore skb header initialization Commit 9f10374bb024 (&amp;#34;can: remove private CAN skb headroom infrastructure&amp;#34;) removed the skb_reset_mac_header()/skb_reset_network_header()/ skb_reset_transport_header() calls from init_can_skb(). As a result, RX skbs from alloc_can_skb() and friends again carry mac_header = 0xFFFF. When such an skb reaches packet_rcv_spkt() (SOCK_PACKET), the push length calculation overflows and triggers skb_under_panic -&amp;gt; kernel BUG -&amp;gt; full machine panic. The same issue was originally reported in 2014 on linux-can and fixed by commit 969439016d2c (&amp;#34;can: add missing initialisations in CAN related skbuffs&amp;#34;). packet_rcv_spkt() itself has never been hardened: only packet_rcv() and tpacket_rcv() gained dev_has_header() checks in commit d549699048b4 (&amp;#34;net/packet: fix packet receive on L3 devices without visible hard header&amp;#34;).&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 127 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: can: dev: init_can_skb(): restore skb header initialization Commit 9f10374bb024 (&amp;#34;can: remove private CAN skb headroom infrastructure&amp;#34;) removed the skb_reset_mac_header()/skb_reset_network_header()/ skb_reset_transport_header() calls from init_can_skb(). As a result, RX skbs from alloc_can_skb() and friends again carry mac_header = 0xFFFF. When such an skb reaches packet_rcv_spkt() (SOCK_PACKET), the push length calculation overflows and triggers skb_under_panic -&amp;gt; kernel BUG -&amp;gt; full machine panic. The same issue was originally reported in 2014 on linux-can and fixed by commit 969439016d2c (&amp;#34;can: add missing initialisations in CAN related skbuffs&amp;#34;). packet_rcv_spkt() itself has never been hardened: only packet_rcv() and tpacket_rcv() gained dev_has_header() checks in commit d549699048b4 (&amp;#34;net/packet: fix packet receive on L3 devices without visible hard header&amp;#34;).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99066</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>
