<?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>Wed, 28 Oct 2026 12:15:11 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-02529</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-02529</link>
      <description>bdu:2026-02529</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-02529</guid>
    </item>
    <item>
      <title>fkie_cve-2025-37835</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-37835</link>
      <description>&lt;p&gt;Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-37835</guid>
    </item>
    <item>
      <title>GHSA-jq24-w46r-q4x4</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jq24-w46r-q4x4</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb: client: Fix netns refcount imbalance causing leaks and use-after-free&lt;/p&gt;
&lt;p&gt;Commit ef7134c7fc48 (&amp;#34;smb: client: Fix use-after-free of network
namespace.&amp;#34;) attempted to fix a netns use-after-free issue by manually
adjusting reference counts via sk-&amp;gt;sk_net_refcnt and sock_inuse_add().&lt;/p&gt;
&lt;p&gt;However, a later commit e9f2517a3e18 (&amp;#34;smb: client: fix TCP timers deadlock
after rmmod&amp;#34;) pointed out that the approach of manually setting
sk-&amp;gt;sk_net_refcnt in the first commit was technically incorrect, as
sk-&amp;gt;sk_net_refcnt should only be set for user sockets. It led to issues
like TCP timers not being cleared properly on close. The second commit
moved to a model of just holding an extra netns reference for
server-&amp;gt;ssocket using get_net(), and dropping it when the server is torn
down.&lt;/p&gt;
&lt;p&gt;But there remain some gaps in the get_net()/put_net() balancing added by
these commits. The incomplete reference handling in these fixes results
in two issues:&lt;/p&gt;
&lt;p&gt;1. Netns refcount leaks[1]&lt;/p&gt;
&lt;p&gt;The problem process is as follows:&lt;/p&gt;
&lt;p&gt;```
mount.cifs                        cifsd&lt;/p&gt;
&lt;p&gt;cifs_do_mount
  cifs_mount
    cifs_mount_get_session
      cifs_get_tcp_session
        get_net()  /* First get net. */
        ip_connect
          generic_ip_connect /* Try port 445 */
            get_net()
            -&amp;gt;connect() /* Failed */
            put_net()
          generic_ip_connect /* Try port 139 */
            get_net() /* Missing matching put_net() for this get_n…&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;smb: client: Fix netns refcount imbalance causing leaks and use-after-free&lt;/p&gt;
&lt;p&gt;Commit ef7134c7fc48 (&amp;#34;smb: client: Fix use-after-free of network
namespace.&amp;#34;) attempted to fix a netns use-after-free issue by manually
adjusting reference counts via sk-&amp;gt;sk_net_refcnt and sock_inuse_add().&lt;/p&gt;
&lt;p&gt;However, a later commit e9f2517a3e18 (&amp;#34;smb: client: fix TCP timers deadlock
after rmmod&amp;#34;) pointed out that the approach of manually setting
sk-&amp;gt;sk_net_refcnt in the first commit was technically incorrect, as
sk-&amp;gt;sk_net_refcnt should only be set for user sockets. It led to issues
like TCP timers not being cleared properly on close. The second commit
moved to a model of just holding an extra netns reference for
server-&amp;gt;ssocket using get_net(), and dropping it when the server is torn
down.&lt;/p&gt;
&lt;p&gt;But there remain some gaps in the get_net()/put_net() balancing added by
these commits. The incomplete reference handling in these fixes results
in two issues:&lt;/p&gt;
&lt;p&gt;1. Netns refcount leaks[1]&lt;/p&gt;
&lt;p&gt;The problem process is as follows:&lt;/p&gt;
&lt;p&gt;```
mount.cifs                        cifsd&lt;/p&gt;
&lt;p&gt;cifs_do_mount
  cifs_mount
    cifs_mount_get_session
      cifs_get_tcp_session
        get_net()  /* First get net. */
        ip_connect
          generic_ip_connect /* Try port 445 */
            get_net()
            -&amp;gt;connect() /* Failed */
            put_net()
          generic_ip_connect /* Try port 139 */
            get_net() /* Missing matching put_net() for this get_n…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jq24-w46r-q4x4</guid>
    </item>
  </channel>
</rss>
