Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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)

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-74563, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected eee2fa6ab3225192d6d894c54a6fb02ac9efdff6 – < f8a8977af2134a1d91e5f9773cb7d9d53278c830
    • affected eee2fa6ab3225192d6d894c54a6fb02ac9efdff6 – < ba95bce5dfe6e2ef602a87e0557225f2934ccb5c
    • affected eee2fa6ab3225192d6d894c54a6fb02ac9efdff6 – < c4933624a6f416ecfcc31ab58d585da1207a0597
    • affected eee2fa6ab3225192d6d894c54a6fb02ac9efdff6 – < 76dd48886eeeb5fcf2b837d2f4c3d17eebeac9ef
    • affected eee2fa6ab3225192d6d894c54a6fb02ac9efdff6 – < f0d1fb05d70c8a561cd8d0473bcacafa2fc137ff
    • affected eee2fa6ab3225192d6d894c54a6fb02ac9efdff6 – < b1d480fce05f857dc438080cd8c9244b84a83494
    • affected eee2fa6ab3225192d6d894c54a6fb02ac9efdff6 – < 8398bc477d3cb3e2b018a5aaac2bec0f69acda30
    • affected eee2fa6ab3225192d6d894c54a6fb02ac9efdff6 – < 78f75d632f74b8de0f081a128588f7c37d0d1164
  • Linux · Linux

    • affected 4.19
    • unaffected < 4.19
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.151 – ≤ 6.6.*
    • unaffected 6.12.103 – ≤ 6.12.*
    • unaffected 6.18.44 – ≤ 6.18.*
    • unaffected 7.1.8 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-74563 badge
[![CVE-2026-74563](https://cveledger.app/badge/CVE-2026-74563.svg)](https://cveledger.app/cve/CVE-2026-74563)

Record last updated .