# net: ipv6: fix NOREF dst use in seg6 and rpl lwtunnels

CVE record · `CVE-2026-46099`

- **Identifiers:** `CVE-2026-46099`
- **State:** Confirmed
- **Severity:** CVSS 8.1 High
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-416](https://cwe.mitre.org/data/definitions/416.html) · [CWE-911](https://cwe.mitre.org/data/definitions/911.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md) · [CWE-911](https://agentprime.io/advisories/tag/cwe-911.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 27 May 2026
- **Updated:** 19 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 27 May 2026, 12:59 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `af4a2209b1344939eaac11f269c261d347cbc3ee to before 51fef5a7c4d160839199e941929456ba21ddf73c` (git)
  - affected: `af4a2209b1344939eaac11f269c261d347cbc3ee to before b258b849a580285a1692e782ebc902b44c884a71` (git)
  - affected: `af4a2209b1344939eaac11f269c261d347cbc3ee to before 6bd17925bd6866027a6555db17905b9fc073d38d` (git)
  - affected: `af4a2209b1344939eaac11f269c261d347cbc3ee to before 52f9db67f8f35f436366cf4980b4f0a2583d0ef0` (git)
  - affected: `af4a2209b1344939eaac11f269c261d347cbc3ee to before b778b6d095421619c331fd2d7751143cd5387103` (git)
  - affected: `af4a2209b1344939eaac11f269c261d347cbc3ee to before 9dd5481f960e337b81d7dfe429529495c1c481c0` (git)
  - affected: `af4a2209b1344939eaac11f269c261d347cbc3ee to before f9c52a6ba9780bd27e0bf4c044fd91c13c778b6e` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.12`
  - unaffected: `before 4.12` (semver)
  - unaffected: `5.15.209 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.175 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.140 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.86 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.27 to 6.18.*, inclusive` (semver)
  - unaffected: `7.0.4 to 7.0.*, inclusive` (semver)
  - unaffected: `7.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 8.1 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`, from CNA (Linux) (used for this record)
- 7.3 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H`, from ADP (redhat-SADP)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0029, the 21st percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 27 May 2026. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2026-46099](https://www.cve.org/CVERecord?id=CVE-2026-46099)
- [NVD: CVE-2026-46099](https://nvd.nist.gov/vuln/detail/CVE-2026-46099)

### References from the CNA

- <https://git.kernel.org/stable/c/51fef5a7c4d160839199e941929456ba21ddf73c>
- <https://git.kernel.org/stable/c/b258b849a580285a1692e782ebc902b44c884a71>
- <https://git.kernel.org/stable/c/6bd17925bd6866027a6555db17905b9fc073d38d>
- <https://git.kernel.org/stable/c/52f9db67f8f35f436366cf4980b4f0a2583d0ef0>
- <https://git.kernel.org/stable/c/b778b6d095421619c331fd2d7751143cd5387103>
- <https://git.kernel.org/stable/c/9dd5481f960e337b81d7dfe429529495c1c481c0>
- <https://git.kernel.org/stable/c/f9c52a6ba9780bd27e0bf4c044fd91c13c778b6e>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-46099>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-46099/>. Everything for agents: <https://agentprime.io/llms.txt>.