High 7.8Published Aug 15, 2026

CVE-2026-74563rds: tcp: hold the RCU lock across ipv6_chk_addr() in rds_tcp_laddr_check()

Updated under an hour ago (2026-10-19 07:23 UTC)

Does this affect you?

It affects Linux. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

In the Linux kernel, the following vulnerability has been resolved: rds: tcp: hold the RCU lock across ipv6_chk_addr() in rds_tcp_laddr_check() rds_tcp_laddr_check() looks up a scoped IPv6 interface with dev_get_by_index_rcu(), drops the RCU read-side lock, and only then passes the bare struct net_device * into ipv6_chk_addr(). dev_get_by_index_rcu() only keeps the device alive within the same RCU read-side section. After rcu_read_unlock(), a concurrent RTM_DELLINK can free the net_device; ipv6_chk_addr() then dereferences the stale pointer in __ipv6_chk_addr_and_flags() (e.g. l3mdev_master_dev_rcu(dev)), reading freed memory. Keep the RCU read-side lock held across the ipv6_chk_addr() call instead of dropping it right after the lookup, so the device cannot be freed while it is in use. BUG: KASAN: slab-use-after-free in __ipv6_chk_addr_and_flags (... net/ipv6/addrconf.c:1998) Read of size 8 at addr ffff8880106ec000 by task exploit/153 Call Trace: ... kasan_report (mm/kasan/report.c:595) __ipv6_chk_addr_and_flags (... net/ipv6/addrconf.c:1998) ipv6_chk_addr (net/ipv6/addrconf.c:2031 net/ipv6/addrconf.c:1972) rds_tcp_laddr_check (net/rds/tcp.c:370) rds_bind (net/rds/bind.c:248) __sys_bind (net/socket.c:1920) __x64_sys_bind (net/socket.c:1956) do_syscall_64 (arch/x86/entry/syscall_64.c:63) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)

CVSS: 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Received
Record last updated: Oct 16, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	from eee2fa6ab3225192d6d894c54a6fb02ac9efdff6 before f8a8977af2134a1d91e5f9773cb7d9d53278c830; from eee2fa6ab3225192d6d894c54a6fb02ac9efdff6 before ba95bce5dfe6e2ef602a87e0557225f2934ccb5c; from eee2fa6ab3225192d6d894c54a6fb02ac9efdff6 before c4933624a6f416ecfcc31ab58d585da1207a0597; from eee2fa6ab3225192d6d894c54a6fb02ac9efdff6 before 76dd48886eeeb5fcf2b837d2f4c3d17eebeac9ef; from eee2fa6ab3225192d6d894c54a6fb02ac9efdff6 before f0d1fb05d70c8a561cd8d0473bcacafa2fc137ff; from eee2fa6ab3225192d6d894c54a6fb02ac9efdff6 before b1d480fce05f857dc438080cd8c9244b84a83494; from eee2fa6ab3225192d6d894c54a6fb02ac9efdff6 before 8398bc477d3cb3e2b018a5aaac2bec0f69acda30; from eee2fa6ab3225192d6d894c54a6fb02ac9efdff6 before 78f75d632f74b8de0f081a128588f7c37d0d1164	CNA record

References

https://git.kernel.org/stable/c/f8a8977af2134a1d91e5f9773cb7d9d53278c830
https://git.kernel.org/stable/c/ba95bce5dfe6e2ef602a87e0557225f2934ccb5c
https://git.kernel.org/stable/c/c4933624a6f416ecfcc31ab58d585da1207a0597
https://git.kernel.org/stable/c/76dd48886eeeb5fcf2b837d2f4c3d17eebeac9ef
https://git.kernel.org/stable/c/f0d1fb05d70c8a561cd8d0473bcacafa2fc137ff
https://git.kernel.org/stable/c/b1d480fce05f857dc438080cd8c9244b84a83494
https://git.kernel.org/stable/c/8398bc477d3cb3e2b018a5aaac2bec0f69acda30
https://git.kernel.org/stable/c/78f75d632f74b8de0f081a128588f7c37d0d1164

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.