<?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, 09 Oct 2026 15:05:37 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38465 — netlink: Fix wraparounds of sk-&gt;sk_rmem_alloc.</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-38465</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, 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: Fix wraparounds of sk-&amp;gt;sk_rmem_alloc.&lt;/p&gt;
&lt;p&gt;Netlink has this pattern in some places&lt;/p&gt;
&lt;p&gt;if (atomic_read(&amp;amp;sk-&amp;gt;sk_rmem_alloc) &amp;gt; sk-&amp;gt;sk_rcvbuf)
  	atomic_add(skb-&amp;gt;truesize, &amp;amp;sk-&amp;gt;sk_rmem_alloc);&lt;/p&gt;
&lt;p&gt;, which has the same problem fixed by commit 5a465a0da13e (&amp;#34;udp:
Fix multiple wraparounds of sk-&amp;gt;sk_rmem_alloc.&amp;#34;).&lt;/p&gt;
&lt;p&gt;For example, if we set INT_MAX to SO_RCVBUFFORCE, the condition
is always false as the two operands are of int.&lt;/p&gt;
&lt;p&gt;Then, a single socket can eat as many skb as possible until OOM
happens, and we can see multiple wraparounds of sk-&amp;gt;sk_rmem_alloc.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s fix it by using atomic_add_return() and comparing the two
variables as unsigned int.&lt;/p&gt;
&lt;p&gt;Before:
  [root@fedora ~]# ss -f netlink
  Recv-Q      Send-Q Local Address:Port                Peer Address:Port
  -1668710080 0               rtnl:nl_wraparound/293               *&lt;/p&gt;
&lt;p&gt;After:
  [root@fedora ~]# ss -f netlink
  Recv-Q     Send-Q Local Address:Port                Peer Address:Port
  2147483072 0               rtnl:nl_wraparound/290               *
  ^
  `--- INT_MAX - 576&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, 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: Fix wraparounds of sk-&amp;gt;sk_rmem_alloc.&lt;/p&gt;
&lt;p&gt;Netlink has this pattern in some places&lt;/p&gt;
&lt;p&gt;if (atomic_read(&amp;amp;sk-&amp;gt;sk_rmem_alloc) &amp;gt; sk-&amp;gt;sk_rcvbuf)
  	atomic_add(skb-&amp;gt;truesize, &amp;amp;sk-&amp;gt;sk_rmem_alloc);&lt;/p&gt;
&lt;p&gt;, which has the same problem fixed by commit 5a465a0da13e (&amp;#34;udp:
Fix multiple wraparounds of sk-&amp;gt;sk_rmem_alloc.&amp;#34;).&lt;/p&gt;
&lt;p&gt;For example, if we set INT_MAX to SO_RCVBUFFORCE, the condition
is always false as the two operands are of int.&lt;/p&gt;
&lt;p&gt;Then, a single socket can eat as many skb as possible until OOM
happens, and we can see multiple wraparounds of sk-&amp;gt;sk_rmem_alloc.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s fix it by using atomic_add_return() and comparing the two
variables as unsigned int.&lt;/p&gt;
&lt;p&gt;Before:
  [root@fedora ~]# ss -f netlink
  Recv-Q      Send-Q Local Address:Port                Peer Address:Port
  -1668710080 0               rtnl:nl_wraparound/293               *&lt;/p&gt;
&lt;p&gt;After:
  [root@fedora ~]# ss -f netlink
  Recv-Q     Send-Q Local Address:Port                Peer Address:Port
  2147483072 0               rtnl:nl_wraparound/290               *
  ^
  `--- INT_MAX - 576&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-38465</guid>
    </item>
  </channel>
</rss>
