<?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>Tue, 29 Sep 2026 01:58:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23419 — net/rds: Fix circular locking dependency in rds_tcp_tune</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23419</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/rds: Fix circular locking dependency in rds_tcp_tune&lt;/p&gt;
&lt;p&gt;syzbot reported a circular locking dependency in rds_tcp_tune() where
sk_net_refcnt_upgrade() is called while holding the socket lock:&lt;/p&gt;
&lt;p&gt;======================================================
WARNING: possible circular locking dependency detected
======================================================
kworker/u10:8/15040 is trying to acquire lock:
ffffffff8e9aaf80 (fs_reclaim){+.+.}-{0:0},
at: __kmalloc_cache_noprof+0x4b/0x6f0&lt;/p&gt;
&lt;p&gt;but task is already holding lock:
ffff88805a3c1ce0 (k-sk_lock-AF_INET6){+.+.}-{0:0},
at: rds_tcp_tune+0xd7/0x930&lt;/p&gt;
&lt;p&gt;The issue occurs because sk_net_refcnt_upgrade() performs memory
allocation (via get_net_track() -&amp;gt; ref_tracker_alloc()) while the
socket lock is held, creating a circular dependency with fs_reclaim.&lt;/p&gt;
&lt;p&gt;Fix this by moving sk_net_refcnt_upgrade() outside the socket lock
critical section. This is safe because the fields modified by the
sk_net_refcnt_upgrade() call (sk_net_refcnt, ns_tracker) are not
accessed by any concurrent code path at this point.&lt;/p&gt;
&lt;p&gt;v2:
  - Corrected fixes tag
  - check patch line wrap nits
  - ai commentary nits&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/rds: Fix circular locking dependency in rds_tcp_tune&lt;/p&gt;
&lt;p&gt;syzbot reported a circular locking dependency in rds_tcp_tune() where
sk_net_refcnt_upgrade() is called while holding the socket lock:&lt;/p&gt;
&lt;p&gt;======================================================
WARNING: possible circular locking dependency detected
======================================================
kworker/u10:8/15040 is trying to acquire lock:
ffffffff8e9aaf80 (fs_reclaim){+.+.}-{0:0},
at: __kmalloc_cache_noprof+0x4b/0x6f0&lt;/p&gt;
&lt;p&gt;but task is already holding lock:
ffff88805a3c1ce0 (k-sk_lock-AF_INET6){+.+.}-{0:0},
at: rds_tcp_tune+0xd7/0x930&lt;/p&gt;
&lt;p&gt;The issue occurs because sk_net_refcnt_upgrade() performs memory
allocation (via get_net_track() -&amp;gt; ref_tracker_alloc()) while the
socket lock is held, creating a circular dependency with fs_reclaim.&lt;/p&gt;
&lt;p&gt;Fix this by moving sk_net_refcnt_upgrade() outside the socket lock
critical section. This is safe because the fields modified by the
sk_net_refcnt_upgrade() call (sk_net_refcnt, ns_tracker) are not
accessed by any concurrent code path at this point.&lt;/p&gt;
&lt;p&gt;v2:
  - Corrected fixes tag
  - check patch line wrap nits
  - ai commentary nits&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23419</guid>
    </item>
  </channel>
</rss>
