CVE-2026-99320 in Linuxinfo

Summary

by MITRE • 11/19/2026

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().

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 11/19/2026

The Linux kernel vulnerability identified as CVE-2024-something involves a critical use-after-free flaw within the IPv6 raw socket implementation, specifically in the function rawv6_send_hdrinc. This issue arises during the processing of outgoing packets where route caching mechanisms interact improperly with Layer 3 device management functions such as l3mdev_ip6_out. The core technical defect lies in the sequence of operations performed by rawv6_send_hdrinc which caches a pointer to an IPv6 destination structure before invoking l3mdev_ip6_out. This function is responsible for handling output paths that may involve Virtual Routing and Forwarding or other network namespace abstractions where the underlying routing logic can dynamically replace the socket buffer destination with a new route object while simultaneously releasing the original cached route via standard kernel memory management routines like dst_destroy triggered through RCU callbacks.

The operational impact of this flaw is severe because it leads to slab-use-after-free conditions that compromise system stability and potentially allow for local privilege escalation or denial of service attacks against network services relying on raw IPv6 sockets. When l3mdev_ip6_out executes, it may invoke vrf_l3_out which queues an RCU callback responsible for freeing the old route object once all pre-existing references are dropped. However, because the code continues to hold and subsequently dereference the stale pointer cached earlier in the function execution flow, there exists a race window where the memory associated with that route structure has already been reclaimed by the kernel's garbage collection mechanisms but is still accessed for statistics accounting or passed as an output device parameter to netfilter hooks via NF_HOOK. This results in undefined behavior including potential kernel panics, data corruption of adjacent heap structures, or exploitation vectors allowing attackers to execute arbitrary code within kernel space if they can control packet contents and timing conditions effectively.

From a vulnerability classification perspective this flaw aligns with CWE-416 which describes use-after-free errors resulting from improper management of memory allocation and deallocation lifecycles particularly in concurrent environments where reference counting or read-copy-update mechanisms are employed incorrectly relative to critical sections boundaries. In terms of adversary tactics it maps closely to ATT&CK technique T1059 Command Scripting when considering how such kernel bugs might be leveraged during post-exploitation phases to maintain persistence or escalate privileges after initial access has been gained through other means although the primary vector here remains local exploitation via crafted network packets sent over raw sockets.

The resolution implemented by Linux kernel developers addresses this issue by restructuring the order of operations within rawv6_send_hdrinc so that route information is reloaded from the current socket buffer destination only after l3mdev_ip6_out has completed its execution rather than relying on a previously cached pointer acquired before potentially mutating functions run. This ensures that any modifications made to skb->dst by intermediate processing layers are properly accounted for and prevents dereferencing freed memory regions thereby eliminating the race condition entirely without requiring changes to broader RCU semantics or network stack architecture which could introduce regressions elsewhere in the system maintaining backward compatibility while fixing this specific concurrency bug effectively closing off exploitation paths associated with stale pointer usage.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/19/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Do you know our Splunk app?

Download it now for free!