CVE-2026-46099

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

A fix is available — apply it.

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 dst_hold() unconditionally. On PREEMPT_RT, ksoftirqd is preemptible and a higher-priority task can release the underlying pcpu_rt between the lookup and the caching through a concurrent FIB lookup on a shared nexthop. Simplified race sequence:

ksoftirqd/X higher-prio task (same CPU X) ----------- -------------------------------- seg6_input_core(,skb)/rpl_input(skb) dst_cache_get() -> miss ip6_route_input(skb) -> ip6_pol_route(,skb,flags) [RT6_LOOKUP_F_DST_NOREF in flags] -> FIB lookup resolves fib6_nh [nhid=N route] -> rt6_make_pcpu_route() [creates pcpu_rt, refcount=1] pcpu_rt->sernum = fib6_sernum [fib6_sernum=W] -> cmpxchg(fib6_nh.rt6i_pcpu, NULL, pcpu_rt) [slot was empty, store succeeds] -> skb_dst_set_noref(skb, dst) [dst is pcpu_rt, refcount still 1]

rt_genid_bump_ipv6() -> bumps fib6_sernum [fib6_sernum from W to Z] ip6_route_output() -> ip6_pol_route() -> FIB lookup resolves fib6_nh [nhid=N] -> rt6_get_pcpu_route() pcpu_rt->sernum != fib6_sernum [W <> Z, stale] -> prev = xchg(rt6i_pcpu, NULL) -> dst_release(prev) [prev is pcpu_rt, refcount 1->0, dead]

dst = skb_dst(skb) [dst is the dead pcpu_rt] dst_cache_set_ip6(dst) -> dst_hold() on dead dst -> WARN / use-after-free

For the race to occur, ksoftirqd must be preemptible (PREEMPT_RT without PREEMPT_RT_NEEDS_BH_LOCK) and a concurrent task must be able to release the pcpu_rt. Shared nexthop objects provide such a path, as two routes pointing to the same nhid share the same fib6_nh and its rt6i_pcpu entry.

Fix seg6_input_core() and rpl_input() by calling skb_dst_force() after ip6_route_input() to force the NOREF dst into a refcounted one before caching. The output path is not affected as ip6_route_output() already returns a refcounted dst.

CVSS v3
8.1
EG Score
8.1(medium)
EPSS
24.1%
KEV
Not listed

Published

May 27, 2026

Last Modified

July 15, 2026

Advisory Details (7)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

net: ipv6: fix NOREF dst use in seg6 and rpl lwtunnels - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f9c52a6ba9780bd27e0bf4c044fd91c13c778b6e
generic

net: ipv6: fix NOREF dst use in seg6 and rpl lwtunnels - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b778b6d095421619c331fd2d7751143cd5387103
generic

net: ipv6: fix NOREF dst use in seg6 and rpl lwtunnels - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b258b849a580285a1692e782ebc902b44c884a71
generic

net: ipv6: fix NOREF dst use in seg6 and rpl lwtunnels - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9dd5481f960e337b81d7dfe429529495c1c481c0
generic

net: ipv6: fix NOREF dst use in seg6 and rpl lwtunnels - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6bd17925bd6866027a6555db17905b9fc073d38d
generic

net: ipv6: fix NOREF dst use in seg6 and rpl lwtunnels - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/52f9db67f8f35f436366cf4980b4f0a2583d0ef0
generic

net: ipv6: fix NOREF dst use in seg6 and rpl lwtunnels - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/51fef5a7c4d160839199e941929456ba21ddf73c

Vendor Advisories for CVE-2026-46099(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 80× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 183 total refreshes for this CVE.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-13 22:30 UTCEPSS rescore
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-11 23:27 UTCEG score recompute
  7. 2026-07-11 23:27 UTCVendor advisory
  8. 2026-07-11 23:27 UTCGHSA enrichment
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-08 23:48 UTCEG score recompute
  12. 2026-07-08 23:48 UTCVendor advisory
  13. 2026-07-08 23:48 UTCGHSA enrichment
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-06 16:27 UTCEPSS rescore
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-01 15:07 UTCEPSS rescore
  21. 2026-07-01 10:08 UTCEG score recompute
  22. 2026-07-01 10:08 UTCVendor advisory
  23. 2026-07-01 10:08 UTCGHSA enrichment
  24. 2026-06-30 23:22 UTCEPSS rescore
  25. 2026-06-30 03:19 UTCEG score recompute
Show 75 more
  1. 2026-06-30 03:19 UTCVendor advisory
  2. 2026-06-30 03:19 UTCGHSA enrichment
  3. 2026-06-29 14:17 UTCEG score recompute
  4. 2026-06-29 14:17 UTCVendor advisory
  5. 2026-06-29 14:17 UTCGHSA enrichment
  6. 2026-06-29 14:06 UTCEPSS rescore
  7. 2026-06-29 14:06 UTCEPSS rescore
  8. 2026-06-28 20:50 UTCEG score recompute
  9. 2026-06-28 20:50 UTCVendor advisory
  10. 2026-06-28 20:50 UTCGHSA enrichment
  11. 2026-06-28 14:07 UTCEPSS rescore
  12. 2026-06-28 06:42 UTCEG score recompute
  13. 2026-06-28 06:42 UTCVendor advisory
  14. 2026-06-28 06:42 UTCGHSA enrichment
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-27 18:28 UTCEG score recompute
  18. 2026-06-27 18:28 UTCVendor advisory
  19. 2026-06-27 18:28 UTCGHSA enrichment
  20. 2026-06-27 05:49 UTCEG score recompute
  21. 2026-06-27 05:49 UTCVendor advisory
  22. 2026-06-27 05:49 UTCGHSA enrichment
  23. 2026-06-27 03:08 UTCEPSS rescore
  24. 2026-06-26 17:05 UTCEG score recompute
  25. 2026-06-26 17:05 UTCVendor advisory
  26. 2026-06-26 17:04 UTCGHSA enrichment
  27. 2026-06-26 02:26 UTCEG score recompute
  28. 2026-06-26 02:26 UTCVendor advisory
  29. 2026-06-26 02:26 UTCGHSA enrichment
  30. 2026-06-25 13:49 UTCEPSS rescore
  31. 2026-06-25 13:09 UTCEG score recompute
  32. 2026-06-25 13:09 UTCVendor advisory
  33. 2026-06-25 13:09 UTCGHSA enrichment
  34. 2026-06-25 00:56 UTCEG score recompute
  35. 2026-06-25 00:56 UTCVendor advisory
  36. 2026-06-25 00:56 UTCGHSA enrichment
  37. 2026-06-24 14:05 UTCEPSS rescore
  38. 2026-06-23 21:33 UTCEPSS rescore
  39. 2026-06-23 21:33 UTCEPSS rescore
  40. 2026-06-22 14:25 UTCEPSS rescore
  41. 2026-06-22 14:25 UTCEPSS rescore
  42. 2026-06-21 14:56 UTCEPSS rescore
  43. 2026-06-21 14:56 UTCEPSS rescore
  44. 2026-06-21 01:59 UTCEPSS rescore
  45. 2026-06-21 01:59 UTCEPSS rescore
  46. 2026-06-19 19:26 UTCEPSS rescore
  47. 2026-06-19 19:26 UTCEPSS rescore
  48. 2026-06-18 17:52 UTCEPSS rescore
  49. 2026-06-18 17:52 UTCEPSS rescore
  50. 2026-06-17 18:42 UTCEG score recompute
  51. 2026-06-17 18:42 UTCGHSA enrichment
  52. 2026-06-17 17:53 UTCEPSS rescore
  53. 2026-06-17 04:14 UTCEG score recompute
  54. 2026-06-17 04:14 UTCGHSA enrichment
  55. 2026-06-16 17:52 UTCEPSS rescore
  56. 2026-06-16 16:06 UTCEG score recompute
  57. 2026-06-16 16:06 UTCVendor advisory
  58. 2026-06-16 16:06 UTCGHSA enrichment
  59. 2026-06-16 01:37 UTCEG score recompute
  60. 2026-06-16 01:37 UTCVendor advisory
  61. 2026-06-16 01:37 UTCGHSA enrichment
  62. 2026-06-15 17:49 UTCEPSS rescore
  63. 2026-06-15 13:29 UTCEG score recompute
  64. 2026-06-15 13:29 UTCVendor advisory
  65. 2026-06-15 13:29 UTCGHSA enrichment
  66. 2026-06-14 20:52 UTCEG score recompute
  67. 2026-06-14 20:52 UTCVendor advisory
  68. 2026-06-14 20:52 UTCGHSA enrichment
  69. 2026-06-14 08:45 UTCEG score recompute
  70. 2026-06-14 08:45 UTCVendor advisory
  71. 2026-06-14 08:45 UTCGHSA enrichment
  72. 2026-06-13 23:00 UTCEPSS rescore
  73. 2026-06-13 20:37 UTCEG score recompute
  74. 2026-06-13 20:37 UTCGHSA enrichment
  75. 2026-06-13 08:04 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-46099?
CVE-2026-46099 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: net: ipv6: fix NOREF dst use in seg6 and rpl lwtunnels seg6inputcore() and rplinput() call ip6route_input() which sets a NOREF dst on the skb, then pass it to dstcacheset_ip6() invoking dst_hold() unconditionally. On PREEMPT_RT,…
When was CVE-2026-46099 disclosed?
CVE-2026-46099 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46099 actively exploited?
CVE-2026-46099 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46099?
CVE-2026-46099 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-46099?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46099, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-46099

Explore →

Is Your Infrastructure Affected by CVE-2026-46099?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.