<?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 15:54:29 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-15746</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-15746</link>
      <description>bdu:2025-15746</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-15746</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-38727</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-38727</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-2025-38727</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0825 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0825</link>
      <description>certfr-2025-avi-0825</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0825</guid>
    </item>
    <item>
      <title>EUVD-2026-364547</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-364547</link>
      <description>EUVD-2026-364547</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-364547</guid>
    </item>
    <item>
      <title>fkie_cve-2025-38727</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-38727</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netlink: avoid infinite retry looping in netlink_unicast()&lt;/p&gt;
&lt;p&gt;netlink_attachskb() checks for the socket&amp;#39;s read memory allocation
constraints. Firstly, it has:&lt;/p&gt;
&lt;p&gt;rmem &amp;lt; READ_ONCE(sk-&amp;gt;sk_rcvbuf)&lt;/p&gt;
&lt;p&gt;to check if the just increased rmem value fits into the socket&amp;#39;s receive
buffer. If not, it proceeds and tries to wait for the memory under:&lt;/p&gt;
&lt;p&gt;rmem + skb-&amp;gt;truesize &amp;gt; READ_ONCE(sk-&amp;gt;sk_rcvbuf)&lt;/p&gt;
&lt;p&gt;The checks don&amp;#39;t cover the case when skb-&amp;gt;truesize + sk-&amp;gt;sk_rmem_alloc is
equal to sk-&amp;gt;sk_rcvbuf. Thus the function neither successfully accepts
these conditions, nor manages to reschedule the task - and is called in
retry loop for indefinite time which is caught as:&lt;/p&gt;
&lt;p&gt;rcu: INFO: rcu_sched self-detected stall on CPU
  rcu:     0-....: (25999 ticks this GP) idle=ef2/1/0x4000000000000000 softirq=262269/262269 fqs=6212
  (t=26000 jiffies g=230833 q=259957)
  NMI backtrace for cpu 0
  CPU: 0 PID: 22 Comm: kauditd Not tainted 5.10.240 #68
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc42 04/01/2014
  Call Trace:
  &amp;lt;IRQ&amp;gt;
  dump_stack lib/dump_stack.c:120
  nmi_cpu_backtrace.cold lib/nmi_backtrace.c:105
  nmi_trigger_cpumask_backtrace lib/nmi_backtrace.c:62
  rcu_dump_cpu_stacks kernel/rcu/tree_stall.h:335
  rcu_sched_clock_irq.cold kernel/rcu/tree.c:2590
  update_process_times kernel/time/timer.c:1953
  tick_sched_handle kernel/time/tick-sched.c:227
  tick_sched_timer kernel/time/tick-sched.c:1399
  __hrtime…&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;netlink: avoid infinite retry looping in netlink_unicast()&lt;/p&gt;
&lt;p&gt;netlink_attachskb() checks for the socket&amp;#39;s read memory allocation
constraints. Firstly, it has:&lt;/p&gt;
&lt;p&gt;rmem &amp;lt; READ_ONCE(sk-&amp;gt;sk_rcvbuf)&lt;/p&gt;
&lt;p&gt;to check if the just increased rmem value fits into the socket&amp;#39;s receive
buffer. If not, it proceeds and tries to wait for the memory under:&lt;/p&gt;
&lt;p&gt;rmem + skb-&amp;gt;truesize &amp;gt; READ_ONCE(sk-&amp;gt;sk_rcvbuf)&lt;/p&gt;
&lt;p&gt;The checks don&amp;#39;t cover the case when skb-&amp;gt;truesize + sk-&amp;gt;sk_rmem_alloc is
equal to sk-&amp;gt;sk_rcvbuf. Thus the function neither successfully accepts
these conditions, nor manages to reschedule the task - and is called in
retry loop for indefinite time which is caught as:&lt;/p&gt;
&lt;p&gt;rcu: INFO: rcu_sched self-detected stall on CPU
  rcu:     0-....: (25999 ticks this GP) idle=ef2/1/0x4000000000000000 softirq=262269/262269 fqs=6212
  (t=26000 jiffies g=230833 q=259957)
  NMI backtrace for cpu 0
  CPU: 0 PID: 22 Comm: kauditd Not tainted 5.10.240 #68
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc42 04/01/2014
  Call Trace:
  &amp;lt;IRQ&amp;gt;
  dump_stack lib/dump_stack.c:120
  nmi_cpu_backtrace.cold lib/nmi_backtrace.c:105
  nmi_trigger_cpumask_backtrace lib/nmi_backtrace.c:62
  rcu_dump_cpu_stacks kernel/rcu/tree_stall.h:335
  rcu_sched_clock_irq.cold kernel/rcu/tree.c:2590
  update_process_times kernel/time/timer.c:1953
  tick_sched_handle kernel/time/tick-sched.c:227
  tick_sched_timer kernel/time/tick-sched.c:1399
  __hrtime…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-38727</guid>
    </item>
    <item>
      <title>GHSA-5j63-8q43-chww</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5j63-8q43-chww</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netlink: avoid infinite retry looping in netlink_unicast()&lt;/p&gt;
&lt;p&gt;netlink_attachskb() checks for the socket&amp;#39;s read memory allocation
constraints. Firstly, it has:&lt;/p&gt;
&lt;p&gt;rmem &amp;lt; READ_ONCE(sk-&amp;gt;sk_rcvbuf)&lt;/p&gt;
&lt;p&gt;to check if the just increased rmem value fits into the socket&amp;#39;s receive
buffer. If not, it proceeds and tries to wait for the memory under:&lt;/p&gt;
&lt;p&gt;rmem + skb-&amp;gt;truesize &amp;gt; READ_ONCE(sk-&amp;gt;sk_rcvbuf)&lt;/p&gt;
&lt;p&gt;The checks don&amp;#39;t cover the case when skb-&amp;gt;truesize + sk-&amp;gt;sk_rmem_alloc is
equal to sk-&amp;gt;sk_rcvbuf. Thus the function neither successfully accepts
these conditions, nor manages to reschedule the task - and is called in
retry loop for indefinite time which is caught as:&lt;/p&gt;
&lt;p&gt;rcu: INFO: rcu_sched self-detected stall on CPU
  rcu:     0-....: (25999 ticks this GP) idle=ef2/1/0x4000000000000000 softirq=262269/262269 fqs=6212
  (t=26000 jiffies g=230833 q=259957)
  NMI backtrace for cpu 0
  CPU: 0 PID: 22 Comm: kauditd Not tainted 5.10.240 #68
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc42 04/01/2014
  Call Trace:
  &amp;lt;IRQ&amp;gt;
  dump_stack lib/dump_stack.c:120
  nmi_cpu_backtrace.cold lib/nmi_backtrace.c:105
  nmi_trigger_cpumask_backtrace lib/nmi_backtrace.c:62
  rcu_dump_cpu_stacks kernel/rcu/tree_stall.h:335
  rcu_sched_clock_irq.cold kernel/rcu/tree.c:2590
  update_process_times kernel/time/timer.c:1953
  tick_sched_handle kernel/time/tick-sched.c:227
  tick_sched_timer kernel/time/tick-sched.c:1399
  __hrtime…&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;netlink: avoid infinite retry looping in netlink_unicast()&lt;/p&gt;
&lt;p&gt;netlink_attachskb() checks for the socket&amp;#39;s read memory allocation
constraints. Firstly, it has:&lt;/p&gt;
&lt;p&gt;rmem &amp;lt; READ_ONCE(sk-&amp;gt;sk_rcvbuf)&lt;/p&gt;
&lt;p&gt;to check if the just increased rmem value fits into the socket&amp;#39;s receive
buffer. If not, it proceeds and tries to wait for the memory under:&lt;/p&gt;
&lt;p&gt;rmem + skb-&amp;gt;truesize &amp;gt; READ_ONCE(sk-&amp;gt;sk_rcvbuf)&lt;/p&gt;
&lt;p&gt;The checks don&amp;#39;t cover the case when skb-&amp;gt;truesize + sk-&amp;gt;sk_rmem_alloc is
equal to sk-&amp;gt;sk_rcvbuf. Thus the function neither successfully accepts
these conditions, nor manages to reschedule the task - and is called in
retry loop for indefinite time which is caught as:&lt;/p&gt;
&lt;p&gt;rcu: INFO: rcu_sched self-detected stall on CPU
  rcu:     0-....: (25999 ticks this GP) idle=ef2/1/0x4000000000000000 softirq=262269/262269 fqs=6212
  (t=26000 jiffies g=230833 q=259957)
  NMI backtrace for cpu 0
  CPU: 0 PID: 22 Comm: kauditd Not tainted 5.10.240 #68
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc42 04/01/2014
  Call Trace:
  &amp;lt;IRQ&amp;gt;
  dump_stack lib/dump_stack.c:120
  nmi_cpu_backtrace.cold lib/nmi_backtrace.c:105
  nmi_trigger_cpumask_backtrace lib/nmi_backtrace.c:62
  rcu_dump_cpu_stacks kernel/rcu/tree_stall.h:335
  rcu_sched_clock_irq.cold kernel/rcu/tree.c:2590
  update_process_times kernel/time/timer.c:1953
  tick_sched_handle kernel/time/tick-sched.c:227
  tick_sched_timer kernel/time/tick-sched.c:1399
  __hrtime…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5j63-8q43-chww</guid>
    </item>
    <item>
      <title>ICSA-25-162-05 — Siemens SIMATIC S7-1500 CPU family</title>
      <link>https://cve.radiocsirt.org/vuln/icsa-25-162-05</link>
      <description>&lt;p&gt;sshd in OpenSSH 6.2 through 8.x before 8.8, when certain non-default configurations are used, allows privilege escalation because supplemental groups are not initialized as expected. Helper programs for AuthorizedKeysCommand and AuthorizedPrincipalsCommand may run with privileges associated with group memberships of the sshd process, if the configuration specifies running the command as a different user. A flaw was found in glibc. When the getaddrinfo function is called with the AF_UNSPEC address family and the system is configured with no-aaaa mode via /etc/resolv.conf, a DNS response via TCP larger than 2048 bytes can potentially disclose stack contents through the function returned address data, and may cause a crash. A flaw was found in glibc. In an extremely rare situation, the getaddrinfo function may access memory that has been freed, resulting in an application crash. This issue is only exploitable when a NSS module implements only the _nss_*_gethostbyname2_r and _nss_*_getcanonname_r hooks without implementing the _nss_*_gethostbyname3_r hook. The resolved name should return a large number of IPv6 and IPv4, and the call to the getaddrinfo function should have the AF_INET6 address family with AI_CANONNAME, AI_ALL and AI_V4MAPPED as flags. A buffer overflow was discovered in the GNU C Library&amp;#39;s dynamic loader ld.so while processing the GLIBC_TUNABLES environment variable. This issue could allow a local attacker to use maliciously crafted GLIBC_TUNABLES environment var…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;sshd in OpenSSH 6.2 through 8.x before 8.8, when certain non-default configurations are used, allows privilege escalation because supplemental groups are not initialized as expected. Helper programs for AuthorizedKeysCommand and AuthorizedPrincipalsCommand may run with privileges associated with group memberships of the sshd process, if the configuration specifies running the command as a different user. A flaw was found in glibc. When the getaddrinfo function is called with the AF_UNSPEC address family and the system is configured with no-aaaa mode via /etc/resolv.conf, a DNS response via TCP larger than 2048 bytes can potentially disclose stack contents through the function returned address data, and may cause a crash. A flaw was found in glibc. In an extremely rare situation, the getaddrinfo function may access memory that has been freed, resulting in an application crash. This issue is only exploitable when a NSS module implements only the _nss_*_gethostbyname2_r and _nss_*_getcanonname_r hooks without implementing the _nss_*_gethostbyname3_r hook. The resolved name should return a large number of IPv6 and IPv4, and the call to the getaddrinfo function should have the AF_INET6 address family with AI_CANONNAME, AI_ALL and AI_V4MAPPED as flags. A buffer overflow was discovered in the GNU C Library&amp;#39;s dynamic loader ld.so while processing the GLIBC_TUNABLES environment variable. This issue could allow a local attacker to use maliciously crafted GLIBC_TUNABLES environment var…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/icsa-25-162-05</guid>
    </item>
    <item>
      <title>NCSC-2026-0147 — Kwetsbaarheden verholpen in Siemens-producten</title>
      <link>https://cve.radiocsirt.org/vuln/ncsc-2026-0147</link>
      <description>NCSC-2026-0147</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ncsc-2026-0147</guid>
    </item>
    <item>
      <title>OESA-2025-2802 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-2802</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nfc: nci: Fix uninit-value in nci_rx_work&lt;/p&gt;
&lt;p&gt;syzbot reported the following uninit-value access issue [1]&lt;/p&gt;
&lt;p&gt;nci_rx_work() parses received packet from ndev-&amp;amp;gt;rx_q. It should be
validated header size, payload size and total packet size before
processing the packet. If an invalid packet is detected, it should be
silently discarded.(CVE-2024-38381)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:net: ti: icssg_prueth: Fix NULL pointer dereference in prueth_probe()In the prueth_probe() function, if one of the calls to emac_phy_connect()fails due to of_phy_connect() returning NULL, then the subsequent call tophy_attached_info() will dereference a NULL pointer.Check the return code of emac_phy_connect and fail cleanly if there is anerror.(CVE-2024-38584)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:cpufreq: exit() callback is optionalThe exit() callback is optional and shouldn t be called without checkinga valid pointer first.Also, we must clear freq_table pointer even if the exit() callback isn tpresent.(CVE-2024-38615)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:serial: max3100: Update uart_driver_registered on driver removalThe removal of the last MAX3100 device triggers the removal ofthe driver. However, code doesn t update the respective globalvariable and after insmod — r…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nfc: nci: Fix uninit-value in nci_rx_work&lt;/p&gt;
&lt;p&gt;syzbot reported the following uninit-value access issue [1]&lt;/p&gt;
&lt;p&gt;nci_rx_work() parses received packet from ndev-&amp;amp;gt;rx_q. It should be
validated header size, payload size and total packet size before
processing the packet. If an invalid packet is detected, it should be
silently discarded.(CVE-2024-38381)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:net: ti: icssg_prueth: Fix NULL pointer dereference in prueth_probe()In the prueth_probe() function, if one of the calls to emac_phy_connect()fails due to of_phy_connect() returning NULL, then the subsequent call tophy_attached_info() will dereference a NULL pointer.Check the return code of emac_phy_connect and fail cleanly if there is anerror.(CVE-2024-38584)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:cpufreq: exit() callback is optionalThe exit() callback is optional and shouldn t be called without checkinga valid pointer first.Also, we must clear freq_table pointer even if the exit() callback isn tpresent.(CVE-2024-38615)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:serial: max3100: Update uart_driver_registered on driver removalThe removal of the last MAX3100 device triggers the removal ofthe driver. However, code doesn t update the respective globalvariable and after insmod — r…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-2802</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:20081-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2025:20081-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:20081-1</guid>
    </item>
    <item>
      <title>SSA-019113 — SSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6</title>
      <link>https://cve.radiocsirt.org/vuln/ssa-019113</link>
      <description>&lt;p&gt;Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).&lt;/p&gt;
&lt;p&gt;Siemens has released new versions for several affected products and recommends to update to the latest versions. Siemens is preparing further fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).&lt;/p&gt;
&lt;p&gt;Siemens has released new versions for several affected products and recommends to update to the latest versions. Siemens is preparing further fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ssa-019113</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:03600-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:03600-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:03600-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38727</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38727</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 112 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netlink: avoid infinite retry looping in netlink_unicast() netlink_attachskb() checks for the socket&amp;#39;s read memory allocation constraints. Firstly, it has:   rmem &amp;lt; READ_ONCE(sk-&amp;gt;sk_rcvbuf) to check if the just increased rmem value fits into the socket&amp;#39;s receive buffer. If not, it proceeds and tries to wait for the memory under:   rmem + skb-&amp;gt;truesize &amp;gt; READ_ONCE(sk-&amp;gt;sk_rcvbuf) The checks don&amp;#39;t cover the case when skb-&amp;gt;truesize + sk-&amp;gt;sk_rmem_alloc is equal to sk-&amp;gt;sk_rcvbuf. Thus the function neither successfully accepts these conditions, nor manages to reschedule the task - and is called in retry loop for indefinite time which is caught as:   rcu: INFO: rcu_sched self-detected stall on CPU   rcu:     0-....: (25999 ticks this GP) idle=ef2/1/0x4000000000000000 softirq=262269/262269 fqs=6212   (t=26000 jiffies g=230833 q=259957)   NMI backtrace for cpu 0   CPU: 0 PID: 22 Comm: kauditd Not tainted 5.10.240 #68   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc42 04/01/2014   Call Trace:   &amp;lt;IRQ&amp;gt;   dump_stack lib/dump_stack.c:120   nmi_cpu_backtrace.cold lib/nmi_backtrace.c:105   nmi_trigger_cpumask_backtrace lib/nmi_backtrace.c:62   rcu_dump_cpu_stacks kernel/rcu/tree_stall.h:335   rcu_sched_clock_irq.cold kernel/rcu/tree.c:2590   update_process_times kernel/time/timer.c:1953   tick_sched_handle kernel/time/tick-sched.c:227   tick_sched_timer kernel/time/tick-sched.c:1399   __hrtimer_run_q…&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 112 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netlink: avoid infinite retry looping in netlink_unicast() netlink_attachskb() checks for the socket&amp;#39;s read memory allocation constraints. Firstly, it has:   rmem &amp;lt; READ_ONCE(sk-&amp;gt;sk_rcvbuf) to check if the just increased rmem value fits into the socket&amp;#39;s receive buffer. If not, it proceeds and tries to wait for the memory under:   rmem + skb-&amp;gt;truesize &amp;gt; READ_ONCE(sk-&amp;gt;sk_rcvbuf) The checks don&amp;#39;t cover the case when skb-&amp;gt;truesize + sk-&amp;gt;sk_rmem_alloc is equal to sk-&amp;gt;sk_rcvbuf. Thus the function neither successfully accepts these conditions, nor manages to reschedule the task - and is called in retry loop for indefinite time which is caught as:   rcu: INFO: rcu_sched self-detected stall on CPU   rcu:     0-....: (25999 ticks this GP) idle=ef2/1/0x4000000000000000 softirq=262269/262269 fqs=6212   (t=26000 jiffies g=230833 q=259957)   NMI backtrace for cpu 0   CPU: 0 PID: 22 Comm: kauditd Not tainted 5.10.240 #68   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc42 04/01/2014   Call Trace:   &amp;lt;IRQ&amp;gt;   dump_stack lib/dump_stack.c:120   nmi_cpu_backtrace.cold lib/nmi_backtrace.c:105   nmi_trigger_cpumask_backtrace lib/nmi_backtrace.c:62   rcu_dump_cpu_stacks kernel/rcu/tree_stall.h:335   rcu_sched_clock_irq.cold kernel/rcu/tree.c:2590   update_process_times kernel/time/timer.c:1953   tick_sched_handle kernel/time/tick-sched.c:227   tick_sched_timer kernel/time/tick-sched.c:1399   __hrtimer_run_q…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38727</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1976 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1976</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder andere nicht 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-Zustand zu erzeugen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1976</guid>
    </item>
  </channel>
</rss>
