CVE-2026-90111ip6mr: do not clone dst in ip6mr_cache_report()
- 7.8HighCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: ip6mr: do not clone dst in ip6mr_cache_report() IPv6 input attaches a non-refcounted (NOREF) dst to skbs under RCU. When an ingress multicast packet misses MFC lookup, ip6mr_cache_unresolved() places the skb onto the unresolved queue, escaping the receive-side RCU grace period. If the underlying route is deleted and freed, and the MFC queue is later resolved with a wrong parent interface, ip6_mr_forward() invokes ip6mr_cache_report(..., MRT6MSG_WRONGMIF), which executes dst_clone(skb_dst(pkt)) on the freed dst entry, triggering a slab use-after-free. Report packets queued to mroute6_sk (a raw socket) and netlink notifications do not require an attached dst entry. Fix this by: 1. Removing dst_clone() in ip6mr_cache_report() and ensuring report skbs do not hold a dst. 2. Dropping skb_dst before queuing unresolved skbs in ip6mr_cache_unresolved(), matching the fact that multicast forwarding resolves outgoing routes anew via ip6_route_output().
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 43 days later
· 43 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 67f415dd29063a5906c560051c00e42dcf01a4dd – < b50d3cfb8513e895cee453dd0f834deee6ccc231
- affected 67f415dd29063a5906c560051c00e42dcf01a4dd – < 7f8287f606c8c028d4224e85d95dc448c6d6d623
- affected 67f415dd29063a5906c560051c00e42dcf01a4dd – < 42ef371466d5648f5c9e8bc219f0af0a2c2bbf8c
- affected 67f415dd29063a5906c560051c00e42dcf01a4dd – < f57b0fd1c62e1be274ee154ab7fb8ac4481b7f89
- affected 67f415dd29063a5906c560051c00e42dcf01a4dd – < 4a674afaae4136c71943aa3e35d433676fd40e8f
- affected 67f415dd29063a5906c560051c00e42dcf01a4dd – < 235b42b5860189eb8c27c36435ad932cae65a734
- affected 5.3
- unaffected < 5.3
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.57 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/b50d3cfb8513e895cee453dd0f834deee6ccc231 (opens in a new tab)
- https://git.kernel.org/stable/c/7f8287f606c8c028d4224e85d95dc448c6d6d623 (opens in a new tab)
- https://git.kernel.org/stable/c/42ef371466d5648f5c9e8bc219f0af0a2c2bbf8c (opens in a new tab)
- https://git.kernel.org/stable/c/f57b0fd1c62e1be274ee154ab7fb8ac4481b7f89 (opens in a new tab)
- https://git.kernel.org/stable/c/4a674afaae4136c71943aa3e35d433676fd40e8f (opens in a new tab)
- https://git.kernel.org/stable/c/235b42b5860189eb8c27c36435ad932cae65a734 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-81704 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-90111)Record last updated .