<?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 15:23:13 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-02759</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-02759</link>
      <description>bdu:2026-02759</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-02759</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-39956</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-39956</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-39956</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1073 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-1073</link>
      <description>certfr-2025-avi-1073</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-1073</guid>
    </item>
    <item>
      <title>EUVD-2026-347270</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-347270</link>
      <description>EUVD-2026-347270</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-347270</guid>
    </item>
    <item>
      <title>fkie_cve-2025-39956</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-39956</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;igc: don&amp;#39;t fail igc_probe() on LED setup error&lt;/p&gt;
&lt;p&gt;When igc_led_setup() fails, igc_probe() fails and triggers kernel panic
in free_netdev() since unregister_netdev() is not called. [1]
This behavior can be tested using fault-injection framework, especially
the failslab feature. [2]&lt;/p&gt;
&lt;p&gt;Since LED support is not mandatory, treat LED setup failures as
non-fatal and continue probe with a warning message, consequently
avoiding the kernel panic.&lt;/p&gt;
&lt;p&gt;[1]
 kernel BUG at net/core/dev.c:12047!
 Oops: invalid opcode: 0000 [#1] SMP NOPTI
 CPU: 0 UID: 0 PID: 937 Comm: repro-igc-led-e Not tainted 6.17.0-rc4-enjuk-tnguy-00865-gc4940196ab02 #64 PREEMPT(voluntary)
 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
 RIP: 0010:free_netdev+0x278/0x2b0
 [...]
 Call Trace:
  &amp;lt;TASK&amp;gt;
  igc_probe+0x370/0x910
  local_pci_probe+0x3a/0x80
  pci_device_probe+0xd1/0x200
 [...]&lt;/p&gt;
&lt;p&gt;[2]
 #!/bin/bash -ex&lt;/p&gt;
&lt;p&gt;FAILSLAB_PATH=/sys/kernel/debug/failslab/
 DEVICE=0000:00:05.0
 START_ADDR=$(grep &amp;#34; igc_led_setup&amp;#34; /proc/kallsyms \
         | awk &amp;#39;{printf(&amp;#34;0x%s&amp;#34;, $1)}&amp;#39;)
 END_ADDR=$(printf &amp;#34;0x%x&amp;#34; $((START_ADDR + 0x100)))&lt;/p&gt;
&lt;p&gt;echo $START_ADDR &amp;gt; $FAILSLAB_PATH/require-start
 echo $END_ADDR &amp;gt; $FAILSLAB_PATH/require-end
 echo 1 &amp;gt; $FAILSLAB_PATH/times
 echo 100 &amp;gt; $FAILSLAB_PATH/probability
 echo N &amp;gt; $FAILSLAB_PATH/ignore-gfp-wait&lt;/p&gt;
&lt;p&gt;echo $DEVICE &amp;gt; /sys/bus/pci/drivers/igc/bind&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;igc: don&amp;#39;t fail igc_probe() on LED setup error&lt;/p&gt;
&lt;p&gt;When igc_led_setup() fails, igc_probe() fails and triggers kernel panic
in free_netdev() since unregister_netdev() is not called. [1]
This behavior can be tested using fault-injection framework, especially
the failslab feature. [2]&lt;/p&gt;
&lt;p&gt;Since LED support is not mandatory, treat LED setup failures as
non-fatal and continue probe with a warning message, consequently
avoiding the kernel panic.&lt;/p&gt;
&lt;p&gt;[1]
 kernel BUG at net/core/dev.c:12047!
 Oops: invalid opcode: 0000 [#1] SMP NOPTI
 CPU: 0 UID: 0 PID: 937 Comm: repro-igc-led-e Not tainted 6.17.0-rc4-enjuk-tnguy-00865-gc4940196ab02 #64 PREEMPT(voluntary)
 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
 RIP: 0010:free_netdev+0x278/0x2b0
 [...]
 Call Trace:
  &amp;lt;TASK&amp;gt;
  igc_probe+0x370/0x910
  local_pci_probe+0x3a/0x80
  pci_device_probe+0xd1/0x200
 [...]&lt;/p&gt;
&lt;p&gt;[2]
 #!/bin/bash -ex&lt;/p&gt;
&lt;p&gt;FAILSLAB_PATH=/sys/kernel/debug/failslab/
 DEVICE=0000:00:05.0
 START_ADDR=$(grep &amp;#34; igc_led_setup&amp;#34; /proc/kallsyms \
         | awk &amp;#39;{printf(&amp;#34;0x%s&amp;#34;, $1)}&amp;#39;)
 END_ADDR=$(printf &amp;#34;0x%x&amp;#34; $((START_ADDR + 0x100)))&lt;/p&gt;
&lt;p&gt;echo $START_ADDR &amp;gt; $FAILSLAB_PATH/require-start
 echo $END_ADDR &amp;gt; $FAILSLAB_PATH/require-end
 echo 1 &amp;gt; $FAILSLAB_PATH/times
 echo 100 &amp;gt; $FAILSLAB_PATH/probability
 echo N &amp;gt; $FAILSLAB_PATH/ignore-gfp-wait&lt;/p&gt;
&lt;p&gt;echo $DEVICE &amp;gt; /sys/bus/pci/drivers/igc/bind&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-39956</guid>
    </item>
    <item>
      <title>GHSA-486r-g5rc-cq67</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-486r-g5rc-cq67</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;igc: don&amp;#39;t fail igc_probe() on LED setup error&lt;/p&gt;
&lt;p&gt;When igc_led_setup() fails, igc_probe() fails and triggers kernel panic
in free_netdev() since unregister_netdev() is not called. [1]
This behavior can be tested using fault-injection framework, especially
the failslab feature. [2]&lt;/p&gt;
&lt;p&gt;Since LED support is not mandatory, treat LED setup failures as
non-fatal and continue probe with a warning message, consequently
avoiding the kernel panic.&lt;/p&gt;
&lt;p&gt;[1]
 kernel BUG at net/core/dev.c:12047!
 Oops: invalid opcode: 0000 [#1] SMP NOPTI
 CPU: 0 UID: 0 PID: 937 Comm: repro-igc-led-e Not tainted 6.17.0-rc4-enjuk-tnguy-00865-gc4940196ab02 #64 PREEMPT(voluntary)
 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
 RIP: 0010:free_netdev+0x278/0x2b0
 [...]
 Call Trace:
  &amp;lt;TASK&amp;gt;
  igc_probe+0x370/0x910
  local_pci_probe+0x3a/0x80
  pci_device_probe+0xd1/0x200
 [...]&lt;/p&gt;
&lt;p&gt;[2]
 #!/bin/bash -ex&lt;/p&gt;
&lt;p&gt;FAILSLAB_PATH=/sys/kernel/debug/failslab/
 DEVICE=0000:00:05.0
 START_ADDR=$(grep &amp;#34; igc_led_setup&amp;#34; /proc/kallsyms \
         | awk &amp;#39;{printf(&amp;#34;0x%s&amp;#34;, $1)}&amp;#39;)
 END_ADDR=$(printf &amp;#34;0x%x&amp;#34; $((START_ADDR + 0x100)))&lt;/p&gt;
&lt;p&gt;echo $START_ADDR &amp;gt; $FAILSLAB_PATH/require-start
 echo $END_ADDR &amp;gt; $FAILSLAB_PATH/require-end
 echo 1 &amp;gt; $FAILSLAB_PATH/times
 echo 100 &amp;gt; $FAILSLAB_PATH/probability
 echo N &amp;gt; $FAILSLAB_PATH/ignore-gfp-wait&lt;/p&gt;
&lt;p&gt;echo $DEVICE &amp;gt; /sys/bus/pci/drivers/igc/bind&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;igc: don&amp;#39;t fail igc_probe() on LED setup error&lt;/p&gt;
&lt;p&gt;When igc_led_setup() fails, igc_probe() fails and triggers kernel panic
in free_netdev() since unregister_netdev() is not called. [1]
This behavior can be tested using fault-injection framework, especially
the failslab feature. [2]&lt;/p&gt;
&lt;p&gt;Since LED support is not mandatory, treat LED setup failures as
non-fatal and continue probe with a warning message, consequently
avoiding the kernel panic.&lt;/p&gt;
&lt;p&gt;[1]
 kernel BUG at net/core/dev.c:12047!
 Oops: invalid opcode: 0000 [#1] SMP NOPTI
 CPU: 0 UID: 0 PID: 937 Comm: repro-igc-led-e Not tainted 6.17.0-rc4-enjuk-tnguy-00865-gc4940196ab02 #64 PREEMPT(voluntary)
 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
 RIP: 0010:free_netdev+0x278/0x2b0
 [...]
 Call Trace:
  &amp;lt;TASK&amp;gt;
  igc_probe+0x370/0x910
  local_pci_probe+0x3a/0x80
  pci_device_probe+0xd1/0x200
 [...]&lt;/p&gt;
&lt;p&gt;[2]
 #!/bin/bash -ex&lt;/p&gt;
&lt;p&gt;FAILSLAB_PATH=/sys/kernel/debug/failslab/
 DEVICE=0000:00:05.0
 START_ADDR=$(grep &amp;#34; igc_led_setup&amp;#34; /proc/kallsyms \
         | awk &amp;#39;{printf(&amp;#34;0x%s&amp;#34;, $1)}&amp;#39;)
 END_ADDR=$(printf &amp;#34;0x%x&amp;#34; $((START_ADDR + 0x100)))&lt;/p&gt;
&lt;p&gt;echo $START_ADDR &amp;gt; $FAILSLAB_PATH/require-start
 echo $END_ADDR &amp;gt; $FAILSLAB_PATH/require-end
 echo 1 &amp;gt; $FAILSLAB_PATH/times
 echo 100 &amp;gt; $FAILSLAB_PATH/probability
 echo N &amp;gt; $FAILSLAB_PATH/ignore-gfp-wait&lt;/p&gt;
&lt;p&gt;echo $DEVICE &amp;gt; /sys/bus/pci/drivers/igc/bind&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-486r-g5rc-cq67</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:20091-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2025:20091-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2025:20091-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:21080-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:21080-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2025:21080-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-39956</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39956</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 90 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: igc: don&amp;#39;t fail igc_probe() on LED setup error When igc_led_setup() fails, igc_probe() fails and triggers kernel panic in free_netdev() since unregister_netdev() is not called. [1] This behavior can be tested using fault-injection framework, especially the failslab feature. [2] Since LED support is not mandatory, treat LED setup failures as non-fatal and continue probe with a warning message, consequently avoiding the kernel panic. [1]  kernel BUG at net/core/dev.c:12047!  Oops: invalid opcode: 0000 [#1] SMP NOPTI  CPU: 0 UID: 0 PID: 937 Comm: repro-igc-led-e Not tainted 6.17.0-rc4-enjuk-tnguy-00865-gc4940196ab02 #64 PREEMPT(voluntary)  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014  RIP: 0010:free_netdev+0x278/0x2b0  [...]  Call Trace:   &amp;lt;TASK&amp;gt;   igc_probe+0x370/0x910   local_pci_probe+0x3a/0x80   pci_device_probe+0xd1/0x200  [...] [2]  #!/bin/bash -ex  FAILSLAB_PATH=/sys/kernel/debug/failslab/  DEVICE=0000:00:05.0  START_ADDR=$(grep &amp;#34; igc_led_setup&amp;#34; /proc/kallsyms \          | awk &amp;#39;{printf(&amp;#34;0x%s&amp;#34;, $1)}&amp;#39;)  END_ADDR=$(printf &amp;#34;0x%x&amp;#34; $((START_ADDR + 0x100)))  echo $START_ADDR &amp;gt; $FAILSLAB_PATH/require-start  echo $END_ADDR &amp;gt; $FAILSLAB_PATH/require-end  echo 1 &amp;gt; $FAILSLAB_PATH/times  echo 100 &amp;gt; $FAILSLAB_PATH/probability  echo N &amp;gt; $FAILSLAB_PATH/ignore-gfp-wait  echo $DEVICE &amp;gt; /sys/bus/pci/drivers/igc/bind&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 90 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: igc: don&amp;#39;t fail igc_probe() on LED setup error When igc_led_setup() fails, igc_probe() fails and triggers kernel panic in free_netdev() since unregister_netdev() is not called. [1] This behavior can be tested using fault-injection framework, especially the failslab feature. [2] Since LED support is not mandatory, treat LED setup failures as non-fatal and continue probe with a warning message, consequently avoiding the kernel panic. [1]  kernel BUG at net/core/dev.c:12047!  Oops: invalid opcode: 0000 [#1] SMP NOPTI  CPU: 0 UID: 0 PID: 937 Comm: repro-igc-led-e Not tainted 6.17.0-rc4-enjuk-tnguy-00865-gc4940196ab02 #64 PREEMPT(voluntary)  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014  RIP: 0010:free_netdev+0x278/0x2b0  [...]  Call Trace:   &amp;lt;TASK&amp;gt;   igc_probe+0x370/0x910   local_pci_probe+0x3a/0x80   pci_device_probe+0xd1/0x200  [...] [2]  #!/bin/bash -ex  FAILSLAB_PATH=/sys/kernel/debug/failslab/  DEVICE=0000:00:05.0  START_ADDR=$(grep &amp;#34; igc_led_setup&amp;#34; /proc/kallsyms \          | awk &amp;#39;{printf(&amp;#34;0x%s&amp;#34;, $1)}&amp;#39;)  END_ADDR=$(printf &amp;#34;0x%x&amp;#34; $((START_ADDR + 0x100)))  echo $START_ADDR &amp;gt; $FAILSLAB_PATH/require-start  echo $END_ADDR &amp;gt; $FAILSLAB_PATH/require-end  echo 1 &amp;gt; $FAILSLAB_PATH/times  echo 100 &amp;gt; $FAILSLAB_PATH/probability  echo N &amp;gt; $FAILSLAB_PATH/ignore-gfp-wait  echo $DEVICE &amp;gt; /sys/bus/pci/drivers/igc/bind&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39956</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2246 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2246</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und 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 einen Denial of Service Angriff durchzuführen und andere nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2246</guid>
    </item>
  </channel>
</rss>
