CVE-2025-21759·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: ipv6: mcast: extend RCU protection in igmp6_send() igmp6_send() can be called without RTNL or RCU being held. Extend RCU protection so that we can safely fetch the net pointer and avoid a potential UAF. Note that we no longer can use sock_alloc_send_skb() because ipv6.igmp_sk uses GFP_KERNEL allocations which can sleep. Instead use alloc_skb() and charge the net->ipv6.igmp_sk socket under RCU protection.
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.13.4
- Published
- 2025-02-27
Affected versions
From: 6.13
Until: 6.13.4
Fixed in: 6.13.4
How to fix this CVE
Update your Linux kernel to version 6.13.4 or later to patch a use-after-free vulnerability in IPv6 multicast handling. The vulnerability occurs when igmp6_send() is called without proper RCU locking, potentially allowing memory corruption. Kernel upgrades should be scheduled during a maintenance window and followed by a system reboot to ensure the new kernel is active.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Check current kernel version: uname -r — ensure it is 6.13.4 or later
- Verify IPv6 multicast is enabled: cat /proc/net/ipv6_route | grep -i mcast or check active IPv6 multicast groups with ip maddr show
- Review kernel logs for memory corruption indicators: sudo dmesg | grep -i 'use-after-free\|UAF\|RCU\|igmp'
- Confirm patch applied after reboot by checking kernel release date: uname -v and cross-reference with kernel.org release history for 6.13.4
FAQ
What is CVE-2025-21759?
CVE-2025-21759 is a use-after-free vulnerability in the Linux kernel's IPv6 multicast (IGMP) implementation. The igmp6_send() function can be called without proper RCU (Read-Copy-Update) locking, potentially allowing a local attacker with low privileges to corrupt kernel memory.
Is CVE-2025-21759 being actively exploited?
No, CVE-2025-21759 is not currently listed in CISA's KEV catalog and no public exploits are available. However, as a high-severity local privilege escalation vector, it should be prioritized for patching.
What versions of Kernel are affected by CVE-2025-21759?
Linux kernel versions 6.13 through 6.13.3 are vulnerable. The fix is available in kernel 6.13.4 and later.
How do I check if my server is vulnerable to CVE-2025-21759?
Run 'uname -r' to check your kernel version. If it shows 6.13.0 through 6.13.3, you are vulnerable. Versions 6.13.4+ or 6.12 and earlier are not affected.
Does Defensia detect CVE-2025-21759?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2025-21759 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2025-21759. Free for 1 server.
Get started free