CVEvulnerability
CVE-2026-90111
7.8 HIGH
Official page ↗
- Status
- Received
- Published
- 2026-09-17
- Last modified
- 2026-10-30
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
- 7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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().
References
- https://git.kernel.org/stable/c/235b42b5860189eb8c27c36435ad932cae65a734 git.kernel.org
- https://git.kernel.org/stable/c/42ef371466d5648f5c9e8bc219f0af0a2c2bbf8c git.kernel.org
- https://git.kernel.org/stable/c/4a674afaae4136c71943aa3e35d433676fd40e8f git.kernel.org
- https://git.kernel.org/stable/c/7f8287f606c8c028d4224e85d95dc448c6d6d623 git.kernel.org
- https://git.kernel.org/stable/c/b50d3cfb8513e895cee453dd0f834deee6ccc231 git.kernel.org
- https://git.kernel.org/stable/c/f57b0fd1c62e1be274ee154ab7fb8ac4481b7f89 git.kernel.org