CVE-2026-99320·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: ipv6: raw: fix use-after-free in rawv6_send_hdrinc() rawv6_send_hdrinc() caches the route before handing the skb to l3mdev_ip6_out(). The VRF output path may replace skb->dst and release the original route, leaving the cached pointer stale. The function later dereferences that pointer for statistics accounting and as the output device passed to NF_HOOK(). Its RCU read-side critical section starts after l3mdev_ip6_out(), so it cannot prevent the old route from being reclaimed in between. Reload the route from the current skb destination after l3mdev_ip6_out() returns. KASAN reports a slab-use-after-free in rawv6_sendmsg(), with the route allocated by ip6_dst_alloc(), freed by dst_destroy() from rcu_core(), and the related RCU callback queued from vrf_l3_out().
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.12.118, 6.18.64, 7.3.5, 7.4-rc2
- Published
How to fix this CVE
Update your Linux kernel to a patched version to resolve this use-after-free vulnerability in IPv6 raw socket handling. If you run kernel 6.12.x, update to 6.12.118 or later; if you run 6.18.x, update to 6.18.64 or later; if you run 7.3.x, update to 7.3.5 or later. Alternatively, install your Linux distribution's latest kernel security updates, which will include the backported fix.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Check your current kernel version with: uname -r
- Verify if your kernel version is earlier than 6.12.118 (6.12.x branch), 6.18.64 (6.18.x branch), or 7.3.5 (7.3.x branch) by comparing version numbers
- Search kernel logs for KASAN reports mentioning 'rawv6_sendmsg' or 'slab-use-after-free': sudo journalctl -b | grep -i 'kasan\|rawv6'
- After applying patches, reboot and confirm the new kernel is loaded with: uname -r, then verify no KASAN errors appear in dmesg: sudo dmesg | grep -i 'kasan'
FAQ
What is CVE-2026-99320?
This is a use-after-free vulnerability in the Linux kernel's IPv6 raw socket implementation where a cached route pointer becomes stale after being replaced by the VRF output path, leading to potential memory corruption when the kernel dereferences the stale pointer for statistics and firewall hooks.
Is CVE-2026-99320 being actively exploited?
No, this vulnerability is not listed on CISA's Known Exploited Vulnerabilities (KEV) catalog and no public exploits are currently available.
What versions of Kernel are affected by CVE-2026-99320?
The vulnerability affects Linux kernel versions prior to 6.12.118 (6.12.x branch), 6.18.64 (6.18.x branch), and 7.3.5 (7.3.x branch). Most enterprise distributions ship kernel versions in these ranges, so checking your specific kernel version is essential.
How do I check if my server is vulnerable to CVE-2026-99320?
Run uname -r to get your kernel version, then compare it against the fixed versions: 6.12.118+, 6.18.64+, or 7.3.5+. If your version is below the respective fix for your branch, your system is vulnerable.
Does Defensia detect CVE-2026-99320?
Yes — Defensia's CVE advisory scanner compares installed kernel package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2026-99320 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-2026-99320. Free for 1 server.
Get started free