CVE-2026-46099 - In the Linux kernel, the following vulnerability has been resolved: net: ipv6: fix NOREF dst use in seg6 and r
CVE-2026-46099 + In the Linux kernel, the following vulnerability has been resolved: net: ipv6: fix NOREF dst use in seg6 and r + High + 2026-05-27
One-sentence business risk
Attackers can turn a normal application path into code execution, making this a direct production-host takeover risk.
Research notes
- Root cause: In the Linux kernel, the following vulnerability has been resolved: net: ipv6: fix NOREF dst use in seg6 and rpl lwtunnels seg6_input_core() and rpl_input() call ip6_route_input() which sets a NOREF dst on the skb, then pass it to dst_cache_set_ip6() invoking.
- Affected versions: through a concurrent FIB lookup on a shared nexthop.
- Fixed / safe versions: Vendor-fixed release or mitigation named by the upstream advisory.
- Public exploit / PoC signal: the consulted NVD/GHSA/vendor sources describe the trigger class; treat it as reproducible until patched.
- CVSS: 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
Exact vulnerable code pattern
run("tool " + user_controlled_value)
Fixed / mitigated code pattern
run(["tool", user_controlled_value], shell=False) with an allowlisted argument schema
Dependency or runtime update:
rg -n "affected component|CVE-2026-46099" .
# update affected runtime/product to Vendor-fixed release or mitigation named by the upstream advisory
Step-by-step integration guide
- Inventory
affected componentacross source, lockfiles, SBOMs, container images, CI images, and deployment manifests. - Upgrade to
Vendor-fixed release or mitigation named by the upstream advisoryor apply the exact vendor patch referenced below. - Replace the vulnerable
command-injectionpattern with the fixed pattern and fail closed on malformed input. - Add a regression test that exercises the advisory trigger and proves the request is rejected, bounded, or authorized.
- Deploy through canary, monitor security logs and resource metrics, then remove temporary edge blocks only after all runtimes are fixed.
Alternative mitigations
- Disable the vulnerable feature path while the package/runtime update rolls out.
- Add WAF or reverse-proxy rules for traversal tokens, prototype-polluting keys, oversized frames, shell metacharacters, or unauthenticated tool calls matching the trigger class.
- Restrict internal egress, rotate exposed secrets, and revoke affected tokens/keys if the vulnerability can disclose config, logs, JWT secrets, proxy credentials, or PKI material.
- For admin/API authorization issues, temporarily require elevated roles and explicit ownership checks at the gateway.
Detection signature
id: cve-2026-46099-in-the-linux-kernel-the-following-vulnerability-
source: NVD bulk JSON feed
dependency_or_product: "affected component"
affected: "through a concurrent FIB lookup on a shared nexthop"
fixed: "Vendor-fixed release or mitigation named by the upstream advisory"
signals:
- "command-injection"
- "../"
- "__proto__"
- "tools/call"
- "wp_ajax_nopriv"
- "pickle.loads"
- "shell command construction"
action: "upgrade, add regression test, and verify deploy artifact"
Copy-paste skill
You are remediating CVE-2026-46099 (In the Linux kernel, the following vulnerability has been resolved: net: ipv6: fix NOREF dst use in seg6 and r) in this repository.
Find every affected dependency, runtime, image, service configuration, and reachable code path. Upgrade or patch to Vendor-fixed release or mitigation named by the upstream advisory. Replace the vulnerable command-injection pattern with a fail-closed implementation, add a regression test for the trigger shape, and update deployment/SBOM artifacts. If this repository does not control the affected runtime, create TRIAGE.md naming the owner, affected version, fixed version, and blocking decision.
Keywords, affected tech stack, and revenue tags
- Keywords:
CVE-2026-46099,command-injection,affected component,NVD bulk JSON feed. - Affected tech stack:
general. - Revenue tags:
sellable_to_fintech,enterprise_blocker,high_priority_sla.
References
- https://access.redhat.com/security/cve/CVE-2026-46099
- https://bugzilla.redhat.com/show_bug.cgi?id=2481972
- https://git.kernel.org/stable/c/51fef5a7c4d160839199e941929456ba21ddf73c
- https://git.kernel.org/stable/c/52f9db67f8f35f436366cf4980b4f0a2583d0ef0
- https://git.kernel.org/stable/c/6bd17925bd6866027a6555db17905b9fc073d38d
- https://git.kernel.org/stable/c/9dd5481f960e337b81d7dfe429529495c1c481c0
- https://git.kernel.org/stable/c/b258b849a580285a1692e782ebc902b44c884a71
- https://git.kernel.org/stable/c/b778b6d095421619c331fd2d7751143cd5387103
- https://git.kernel.org/stable/c/f9c52a6ba9780bd27e0bf4c044fd91c13c778b6e
- https://nvd.nist.gov/vuln/detail/CVE-2026-46099
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-46099.json