CVE-2025-21760
massUse-After-Free in Linux Kernel IPv6 Neighbor Discovery (ndisc_send_skb)
CVE-2025-21760 is a use-after-free (CWE-416) in the Linux kernel's IPv6 Neighbor Discovery code: ndisc_send_skb() can be reached without RTNL or RCU read-side protection held, so a concurrent teardown (such as interface or network-namespace removal) can free memory the send path is still using. The fix acquires rcu_read_lock() earlier so that dev_net_rcu() can be used safely, closing the race window. A successful race could corrupt kernel memory and, per the CVSS vector (AV:N, AC:H), compromise the confidentiality, integrity, and availability of the host, although the high attack complexity makes reliable exploitation difficult. Any Linux system with IPv6 enabled is exposed in principle, which covers most servers, cloud instances, containers, Android devices, and embedded Linux deployments. No public proof-of-concept or confirmed in-the-wild exploitation is known, but a 36.8% EPSS score (98th percentile) indicates a materially elevated likelihood of exploitation within 30 days.
What to do: Apply your distribution's or vendor's latest kernel security update containing the upstream fix "ndisc: extend RCU protection in ndisc_send_skb()" and verify the running kernel version afterward. Prioritize internet-facing and IPv6-enabled hosts; because this is a hard-to-hit timing race rather than a straightforwardly packet-triggered bug, there is no dependable configuration-level mitigation beyond patching.
| Linux kernel | — |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
In the Linux kernel, the following vulnerability has been resolved: ndisc: extend RCU protection in ndisc_send_skb() ndisc_send_skb() can be called without RTNL or RCU held. Acquire rcu_read_lock() earlier, so that we can use dev_net_rcu() and avoid a potential UAF.
- Vendors
- linux
- Products
- linux kernel
- Weakness
- CWE-416
- Vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
In the news0 stories
No ingested article mentions this CVE yet.