nday
CVE-2026-46099

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

Linux / Linux

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

use-after-free
CWE-416, stated by the ADP CISA-ADP and NVD, republishing 134c704f-9b21-4f2e-91b3-4a467353bcc0
remote, unauthenticated
AV:N, PR:N, UI:N in CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
network
AV:N in CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
no authentication required
PR:N in CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
no user interaction
UI:N in CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
Linux kernel
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernel
operating system
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernelthe product type of Linux kernel in nday's product registry
stage
DIS
disclosed
cvss
8.1 HIGH v3.1

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
05-27T12:59Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

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.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:H
High: success depends on conditions outside the attacker's control, such as gathering details of the target or winning a race
Privileges required PR:N
None: no account or authorization needed
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS 3.1 vector from the CVE record, scored by the CNA Linux.

Event log

+DISdisclosed

CVE record published by Linux. CVSS 8.1, high.

src cvelist · nday , bulk import · raw
{
  "id": 426168,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-46099",
  "occurred_at": "2026-05-27T12:59:04.628Z",
  "observed_at": "2026-11-13T05:39:50.021609Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "version": "3.1",
      "base_score": 8.1,
      "base_severity": "HIGH"
    },
    "ssvc": {
      "timestamp": "2026-10-16T15:19:34.914201Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2026-05-27T12:59:04.628Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.