CVE-2026-90111

ip6mr: do not clone dst in ip6mr_cache_report()

Published Sep 17, 2026 CVSS 3.1 · 7.8 High EPSS < 1% KEV · Not listed
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().

Analysis

AI-generated

Technical impact

The flaw resides in the IPv6 multicast routing subsystem of the Linux kernel. When a multicast packet arrives on a link that lacks a valid Multicast Forwarding Cache (MFC) entry, the packet is queued in an unresolved state while its destination cache (dst) entry is freed. Subsequent resolution of the MFC with an incorrect parent interface triggers a report routine that clones the now‑freed dst reference, leading to a slab use‑after‑free. The resulting memory corruption can crash the kernel or allow an attacker to execute arbitrary code. The weakness aligns with CWE‑416: Use‑After‑Free.

Affected Systems

Any Linux deployment running a kernel version that contains the legacy ip6mr_cache_report routine and that forwards IPv6 multicast traffic is vulnerable. Specific version information is not provided in the advisory, so all kernels older than the applied patch are considered affected. Systems that enable the ip6_multicast forwarding feature and expose themselves to external IPv6 multicast traffic are at greatest risk.

Risk and Exploitability

The CVSS score of 7.8 flags a high‑severity condition, while the EPSS score of less than 1% indicates a low probability of exploitation in the wild. The vulnerability is not listed in the CISA KEV catalog, further reducing the perceived threat level. Exploitation requires an attacker who can inject crafted IPv6 multicast packets onto the network path that traverses the vulnerable host. An attacker who successfully triggers the use‑after‑free could cause a kernel panic, forcing a reboot (Denial of Service), or possibly execute arbitrary code if memory is overwritten with malicious data.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that includes the patch removing dst_clone() in ip6mr_cache_report() and correcting the unresolved skb handling.
  • If an immediate kernel update is not possible, block or disable IPv6 multicast forwarding on the affected host to prevent the triggering of the vulnerable code paths.
  • After applying the fix or enforcing the network restriction, monitor system logs for kernel panics or abnormal crashes that might indicate lingering memory corruption; trigger an incident response if such events occur.

Generated by OpenCVE AI on September 20, 2026 at 02:54 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4904-1 linux-6.12 security update
Debian DLA Debian DLA DLA-4906-1 linux security update
Ubuntu USN Ubuntu USN USN-9019-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9020-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9091-1 Linux kernel (NVIDIA Tegra) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
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().
Title ip6mr: do not clone dst in ip6mr_cache_report()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 30, 2026, 12:34 PM
Reserved
Sep 11, 2026, 7:38 PM
Status
Received
Published
Sep 17, 2026, 5:17 PM
Modified
Oct 30, 2026, 1:20 PM