<?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://vulnerability.circl.lu</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 23:36:01 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38727 — netlink: avoid infinite retry looping in netlink_unicast()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38727</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC CN 4100, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&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;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC CN 4100, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&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://vulnerability.circl.lu/vuln/cve-2025-38727</guid>
    </item>
  </channel>
</rss>
