Skip to main content
VulnerabilityPublished Updated

CVE-2026-23419: Linux kernel · net/rds: Fix circular locking dependency in rds_tcp_tune

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-23419· High 7.5

Not known to be exploited · CVSS 7.5 High · fixed in ce5be6703afd2ac2ff7dabd397137d71d22d4bc3 : patch Linux kernel soon.

Data as of 30 Oct 2026, 16:33 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Linux)CVSS 3.17.5
Patch
Available – fixed in ce5be6703afd2ac2ff7dabd397137d71d22d4bc3, 8519e6883a942e510f33a0e634e27bcc3a844a40, 026bbaeeab9e04534ee58882b6447300629b42f6 +4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=5.17.7 <5.18
Fixed in
  • ce5be6703afd2ac2ff7dabd397137d71d22d4bc3
  • 8519e6883a942e510f33a0e634e27bcc3a844a40
  • 026bbaeeab9e04534ee58882b6447300629b42f6
  • 8babb271403378ba6836f6c8599c5313d0e2355d
  • 6ce948fa54599f369ff7fe8b793a6aae4b0762b2
  • 6a877ececd6daa002a9a0002cd0fbca6592a9244
  • 5.18
LinuxLinuxAffected
  • =5.18
Fixed in–

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

References

Community reviews

Loading reviews…