CVE 7.5 HIGH

net/rds: Fix circular locking dependency in rds_tcp_tune_CVE-2026-23419

7.5 / 10
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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

Basic Information

ID CVE-2026-23419
Source Linux
Published Apr 3, 2026 at 13:24
Modified Apr 27, 2026 at 14:02

Affected Product

Vendor Linux
Product Linux
Version 3a58f13a881ed351198ffab4cf9953cf19d2ab3a
Affected Versions Linux Linux 3a58f13a881ed351198ffab4cf9953cf19d2ab3a
Linux Linux 3a58f13a881ed351198ffab4cf9953cf19d2ab3a
Linux Linux 3a58f13a881ed351198ffab4cf9953cf19d2ab3a
Linux Linux 3a58f13a881ed351198ffab4cf9953cf19d2ab3a
Linux Linux 3a58f13a881ed351198ffab4cf9953cf19d2ab3a
Linux Linux 2a6efabed754c9dcf27e6def71317b374f58a852
Linux Linux 5.18

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.