All reports
Medium

kernel: net/rds: Fix circular locking dependency in rds_tcp_tune

Affected versions

Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-23419

Probability of exploitation in the next 30 days: 0.28%

FIRST EPSS · 2026-11-21

Description

In the Linux kernel, the following vulnerability has been resolved: net/rds: Fix circular locking dependency in rds_tcp_tune syzbot reported a circular locking dependency in rds_tcp_tune() where sk_net_refcnt_upgrade() is called while holding the socket lock:

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 but task is already holding lock: ffff88805a3c1ce0 (k-sk_lock-AF_INET6){+.+.}-{0:0}, at: rds_tcp_tune+0xd7/0x930 The issue occurs because sk_net_refcnt_upgrade() performs memory allocation (via get_net_track() -> ref_tracker_alloc()) while the socket lock is held, creating a circular dependency with fs_reclaim. 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. v2:

  • Corrected fixes tag

  • check patch line wrap nits

  • ai commentary nits

A flaw was found in the Linux kernel's net/rds module. This vulnerability involves a circular locking dependency within the rds_tcp_tune() function. The issue arises when the sk_net_refcnt_upgrade() function performs memory allocation while a socket lock is held, creating a deadlock with the fs_reclaim lock. This can lead to system unresponsiveness or crashes, resulting in a Denial of Service (DoS) condition.