<?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>Sat, 03 Oct 2026 07:20:38 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03511</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03511</link>
      <description>bdu:2026-03511</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03511</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0252 — 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-0252</link>
      <description>certfr-2025-avi-0252</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0252</guid>
    </item>
    <item>
      <title>EUVD-2026-310519</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310519</link>
      <description>EUVD-2026-310519</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310519</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49379</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49379</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;driver core: Fix wait_for_device_probe() &amp;amp; deferred_probe_timeout interaction&lt;/p&gt;
&lt;p&gt;Mounting NFS rootfs was timing out when deferred_probe_timeout was
non-zero [1].  This was because ip_auto_config() initcall times out
waiting for the network interfaces to show up when
deferred_probe_timeout was non-zero. While ip_auto_config() calls
wait_for_device_probe() to make sure any currently running deferred
probe work or asynchronous probe finishes, that wasn&amp;#39;t sufficient to
account for devices being deferred until deferred_probe_timeout.&lt;/p&gt;
&lt;p&gt;Commit 35a672363ab3 (&amp;#34;driver core: Ensure wait_for_device_probe() waits
until the deferred_probe_timeout fires&amp;#34;) tried to fix that by making
sure wait_for_device_probe() waits for deferred_probe_timeout to expire
before returning.&lt;/p&gt;
&lt;p&gt;However, if wait_for_device_probe() is called from the kernel_init()
context:&lt;/p&gt;
&lt;p&gt;- Before deferred_probe_initcall() [2], it causes the boot process to
  hang due to a deadlock.&lt;/p&gt;
&lt;p&gt;- After deferred_probe_initcall() [3], it blocks kernel_init() from
  continuing till deferred_probe_timeout expires and beats the point of
  deferred_probe_timeout that&amp;#39;s trying to wait for userspace to load
  modules.&lt;/p&gt;
&lt;p&gt;Neither of this is good. So revert the changes to
wait_for_device_probe().&lt;/p&gt;
&lt;p&gt;[1] - https://lore.kernel.org/lkml/TYAPR01MB45443DF63B9EF29054F7C41FD8C60@TYAPR01MB4544.jpnprd01.prod.outlook.com/
[2] - https://lore.kernel.org/lkml/YowHNo4sBjr9ijZr@dev-arch.thelio-3990X/
[…&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;driver core: Fix wait_for_device_probe() &amp;amp; deferred_probe_timeout interaction&lt;/p&gt;
&lt;p&gt;Mounting NFS rootfs was timing out when deferred_probe_timeout was
non-zero [1].  This was because ip_auto_config() initcall times out
waiting for the network interfaces to show up when
deferred_probe_timeout was non-zero. While ip_auto_config() calls
wait_for_device_probe() to make sure any currently running deferred
probe work or asynchronous probe finishes, that wasn&amp;#39;t sufficient to
account for devices being deferred until deferred_probe_timeout.&lt;/p&gt;
&lt;p&gt;Commit 35a672363ab3 (&amp;#34;driver core: Ensure wait_for_device_probe() waits
until the deferred_probe_timeout fires&amp;#34;) tried to fix that by making
sure wait_for_device_probe() waits for deferred_probe_timeout to expire
before returning.&lt;/p&gt;
&lt;p&gt;However, if wait_for_device_probe() is called from the kernel_init()
context:&lt;/p&gt;
&lt;p&gt;- Before deferred_probe_initcall() [2], it causes the boot process to
  hang due to a deadlock.&lt;/p&gt;
&lt;p&gt;- After deferred_probe_initcall() [3], it blocks kernel_init() from
  continuing till deferred_probe_timeout expires and beats the point of
  deferred_probe_timeout that&amp;#39;s trying to wait for userspace to load
  modules.&lt;/p&gt;
&lt;p&gt;Neither of this is good. So revert the changes to
wait_for_device_probe().&lt;/p&gt;
&lt;p&gt;[1] - https://lore.kernel.org/lkml/TYAPR01MB45443DF63B9EF29054F7C41FD8C60@TYAPR01MB4544.jpnprd01.prod.outlook.com/
[2] - https://lore.kernel.org/lkml/YowHNo4sBjr9ijZr@dev-arch.thelio-3990X/
[…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49379</guid>
    </item>
    <item>
      <title>GHSA-2v76-ghxq-9xvj</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2v76-ghxq-9xvj</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;driver core: Fix wait_for_device_probe() &amp;amp; deferred_probe_timeout interaction&lt;/p&gt;
&lt;p&gt;Mounting NFS rootfs was timing out when deferred_probe_timeout was
non-zero [1].  This was because ip_auto_config() initcall times out
waiting for the network interfaces to show up when
deferred_probe_timeout was non-zero. While ip_auto_config() calls
wait_for_device_probe() to make sure any currently running deferred
probe work or asynchronous probe finishes, that wasn&amp;#39;t sufficient to
account for devices being deferred until deferred_probe_timeout.&lt;/p&gt;
&lt;p&gt;Commit 35a672363ab3 (&amp;#34;driver core: Ensure wait_for_device_probe() waits
until the deferred_probe_timeout fires&amp;#34;) tried to fix that by making
sure wait_for_device_probe() waits for deferred_probe_timeout to expire
before returning.&lt;/p&gt;
&lt;p&gt;However, if wait_for_device_probe() is called from the kernel_init()
context:&lt;/p&gt;
&lt;p&gt;- Before deferred_probe_initcall() [2], it causes the boot process to
  hang due to a deadlock.&lt;/p&gt;
&lt;p&gt;- After deferred_probe_initcall() [3], it blocks kernel_init() from
  continuing till deferred_probe_timeout expires and beats the point of
  deferred_probe_timeout that&amp;#39;s trying to wait for userspace to load
  modules.&lt;/p&gt;
&lt;p&gt;Neither of this is good. So revert the changes to
wait_for_device_probe().&lt;/p&gt;
&lt;p&gt;[1] - https://lore.kernel.org/lkml/TYAPR01MB45443DF63B9EF29054F7C41FD8C60@TYAPR01MB4544.jpnprd01.prod.outlook.com/
[2] - https://lore.kernel.org/lkml/YowHNo4sBjr9ijZr@dev-arch.thelio-3990X/
[…&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;driver core: Fix wait_for_device_probe() &amp;amp; deferred_probe_timeout interaction&lt;/p&gt;
&lt;p&gt;Mounting NFS rootfs was timing out when deferred_probe_timeout was
non-zero [1].  This was because ip_auto_config() initcall times out
waiting for the network interfaces to show up when
deferred_probe_timeout was non-zero. While ip_auto_config() calls
wait_for_device_probe() to make sure any currently running deferred
probe work or asynchronous probe finishes, that wasn&amp;#39;t sufficient to
account for devices being deferred until deferred_probe_timeout.&lt;/p&gt;
&lt;p&gt;Commit 35a672363ab3 (&amp;#34;driver core: Ensure wait_for_device_probe() waits
until the deferred_probe_timeout fires&amp;#34;) tried to fix that by making
sure wait_for_device_probe() waits for deferred_probe_timeout to expire
before returning.&lt;/p&gt;
&lt;p&gt;However, if wait_for_device_probe() is called from the kernel_init()
context:&lt;/p&gt;
&lt;p&gt;- Before deferred_probe_initcall() [2], it causes the boot process to
  hang due to a deadlock.&lt;/p&gt;
&lt;p&gt;- After deferred_probe_initcall() [3], it blocks kernel_init() from
  continuing till deferred_probe_timeout expires and beats the point of
  deferred_probe_timeout that&amp;#39;s trying to wait for userspace to load
  modules.&lt;/p&gt;
&lt;p&gt;Neither of this is good. So revert the changes to
wait_for_device_probe().&lt;/p&gt;
&lt;p&gt;[1] - https://lore.kernel.org/lkml/TYAPR01MB45443DF63B9EF29054F7C41FD8C60@TYAPR01MB4544.jpnprd01.prod.outlook.com/
[2] - https://lore.kernel.org/lkml/YowHNo4sBjr9ijZr@dev-arch.thelio-3990X/
[…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2v76-ghxq-9xvj</guid>
    </item>
    <item>
      <title>RHSA-2023:2458 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2023:2458</link>
      <description>&lt;p&gt;hw: cpu: AMD CPUs may transiently execute beyond unconditional direct branch kernel: ext4: kernel bug in ext4_write_inline_data_end() kernel: malicious data for FBIOPUT_VSCREENINFO ioctl may cause OOB write memory kernel: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs kernel: mlxsw: thermal: Fix out-of-bounds memory accesses kernel: mlxsw: spectrum: Protect driver from buggy firmware kernel: net: stmmac: fix tc flower deletion for VLAN priority Rx steering kernel: can: etas_es58x: es58x_rx_err_msg(): fix memory leak in error path kernel: possible race condition in drivers/tty/tty_buffers.c kernel: KVM: NULL pointer dereference in kvm_mmu_invpcid_gva kernel: use-after-free in free_pipe_info() could lead to privilege escalation kernel: KVM: nVMX: missing IBPB when exiting from nested guest can lead to Spectre v2 attacks kernel: netfilter: nf_conntrack_irc message handling issue kernel: race condition in xfrm_probe_algs can lead to OOB read/write kernel: out-of-bounds read in fib_nh_match of the file net/ipv4/fib_semantics.c kernel: race condition in hugetlb_no_page() in mm/hugetlb.c kernel: memory leak in ipv6_renew_options() kernel: data races around icsk-&amp;gt;icsk_af_ops in do_ipv6_setsockopt kernel: data races around sk-&amp;gt;sk_prot kernel: memory leak in l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c kernel: denial of service in follow_page_pte in mm/gup.c due to poisoned pte entry kernel: use-after-free after failed devlink relo…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;hw: cpu: AMD CPUs may transiently execute beyond unconditional direct branch kernel: ext4: kernel bug in ext4_write_inline_data_end() kernel: malicious data for FBIOPUT_VSCREENINFO ioctl may cause OOB write memory kernel: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs kernel: mlxsw: thermal: Fix out-of-bounds memory accesses kernel: mlxsw: spectrum: Protect driver from buggy firmware kernel: net: stmmac: fix tc flower deletion for VLAN priority Rx steering kernel: can: etas_es58x: es58x_rx_err_msg(): fix memory leak in error path kernel: possible race condition in drivers/tty/tty_buffers.c kernel: KVM: NULL pointer dereference in kvm_mmu_invpcid_gva kernel: use-after-free in free_pipe_info() could lead to privilege escalation kernel: KVM: nVMX: missing IBPB when exiting from nested guest can lead to Spectre v2 attacks kernel: netfilter: nf_conntrack_irc message handling issue kernel: race condition in xfrm_probe_algs can lead to OOB read/write kernel: out-of-bounds read in fib_nh_match of the file net/ipv4/fib_semantics.c kernel: race condition in hugetlb_no_page() in mm/hugetlb.c kernel: memory leak in ipv6_renew_options() kernel: data races around icsk-&amp;gt;icsk_af_ops in do_ipv6_setsockopt kernel: data races around sk-&amp;gt;sk_prot kernel: memory leak in l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c kernel: denial of service in follow_page_pte in mm/gup.c due to poisoned pte entry kernel: use-after-free after failed devlink relo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2023:2458</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:1176-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:1176-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:1176-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49379</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49379</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 92 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: driver core: Fix wait_for_device_probe() &amp;amp; deferred_probe_timeout interaction Mounting NFS rootfs was timing out when deferred_probe_timeout was non-zero [1].  This was because ip_auto_config() initcall times out waiting for the network interfaces to show up when deferred_probe_timeout was non-zero. While ip_auto_config() calls wait_for_device_probe() to make sure any currently running deferred probe work or asynchronous probe finishes, that wasn&amp;#39;t sufficient to account for devices being deferred until deferred_probe_timeout. Commit 35a672363ab3 (&amp;#34;driver core: Ensure wait_for_device_probe() waits until the deferred_probe_timeout fires&amp;#34;) tried to fix that by making sure wait_for_device_probe() waits for deferred_probe_timeout to expire before returning. However, if wait_for_device_probe() is called from the kernel_init() context: - Before deferred_probe_initcall() [2], it causes the boot process to   hang due to a deadlock. - After deferred_probe_initcall() [3], it blocks kernel_init() from   continuing till deferred_probe_timeout expires and beats the point of   deferred_probe_timeout that&amp;#39;s trying to wait for userspace to load   modules. Neither of this is good. So revert the changes to wait_for_device_probe(). [1] - https://lore.kernel.org/lkml/TYAPR01MB45443DF63B9EF29054F7C41FD8C60@TYAPR01MB4544.jpnprd01.prod.outlook.com/ [2] - https://lore.kernel.org/lkml/YowHNo4sBjr9ijZr@dev-arch.thelio-3990X/ [3] - htt…&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 92 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: driver core: Fix wait_for_device_probe() &amp;amp; deferred_probe_timeout interaction Mounting NFS rootfs was timing out when deferred_probe_timeout was non-zero [1].  This was because ip_auto_config() initcall times out waiting for the network interfaces to show up when deferred_probe_timeout was non-zero. While ip_auto_config() calls wait_for_device_probe() to make sure any currently running deferred probe work or asynchronous probe finishes, that wasn&amp;#39;t sufficient to account for devices being deferred until deferred_probe_timeout. Commit 35a672363ab3 (&amp;#34;driver core: Ensure wait_for_device_probe() waits until the deferred_probe_timeout fires&amp;#34;) tried to fix that by making sure wait_for_device_probe() waits for deferred_probe_timeout to expire before returning. However, if wait_for_device_probe() is called from the kernel_init() context: - Before deferred_probe_initcall() [2], it causes the boot process to   hang due to a deadlock. - After deferred_probe_initcall() [3], it blocks kernel_init() from   continuing till deferred_probe_timeout expires and beats the point of   deferred_probe_timeout that&amp;#39;s trying to wait for userspace to load   modules. Neither of this is good. So revert the changes to wait_for_device_probe(). [1] - https://lore.kernel.org/lkml/TYAPR01MB45443DF63B9EF29054F7C41FD8C60@TYAPR01MB4544.jpnprd01.prod.outlook.com/ [2] - https://lore.kernel.org/lkml/YowHNo4sBjr9ijZr@dev-arch.thelio-3990X/ [3] - htt…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49379</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2107 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2107</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.&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 oder nicht näher beschriebene Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2107</guid>
    </item>
  </channel>
</rss>
