CVE-2026-90111
HighCVSS 7.8Exploitation Probability (EPSS)
Low risk6th percentile - higher than 6% of all known CVEs
Summary
In the Linux kernel IPv6 multicast routing (ip6mr) subsystem, incoming packets attach a non-refcounted (NOREF) dst under RCU. When an ingress multicast packet misses MFC lookup, it is placed on 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, ip6mr_cache_report() executes dst_clone() on the freed dst entry, triggering a use-after-free.
Risk Assessment
This can lead to a slab use-after-free and kernel crash. The risk affects systems with IPv6 multicast routing enabled.
Recommendation
Update the Linux kernel to a version with the fix. Restrict the ability to send IPv6 multicast traffic from untrusted sources.
Related vulnerabilities
- CVE-2026-63774Critical
Insufficient input validation in the PowerSYSTEM Center report designer allows an authenticated user to execute unauthorized SQL commands.
- CVE-2026-63017Critical
Incorrect authorization in PowerSYSTEM Center allows a low-privileged, authenticated user to access resources normally limited to administrators.
- CVE-2026-77596Critical
In Kubeflow Pipelines prior to 2.18.0, the multi-user HTTP endpoints for uploading pipelines and pipeline versions skip SubjectAccessReview when the target namespace is empty and REQUIRE_NAMESPACE_FOR_PIPELINES defaults to false. A low-privilege tenant can create shared pipelines or inject attacker-controlled versions into existing shared pipelines without the required write permission. If the API server is directly reachable without an authenticating proxy, an unauthenticated caller can exploit the same bypass.
- CVE-2026-119757Critical
BTCPay Server before 2.4.2, including 2.4.2 release candidates, contains an information disclosure vulnerability that allows unauthenticated remote attackers to retrieve .macaroon credential files for an LND node. The exposed macaroon can be used to gain full control of the LND node, including moving funds, resulting in theft of funds.
- CVE-2026-111494Critical
The MatchPoint Android app incorrectly validates TLS certificates due to a TrustManager that accepts any certificate and a permissive hostname validator. The app also allows unencrypted HTTP traffic, enabling an attacker who intercepts traffic to read and modify communications, including credentials and personal data.
- CVE-2026-111490Critical
An insecure direct object reference (IDOR) vulnerability in the MatchPoint API relies on the `actingasuser` HTTP header without verifying the requester's authorization for the specified user. Manipulation of sequential identifiers allows access to personal, banking, and financial data, private messages, and physical-access QR codes, as well as modification of third-party accounts, password changes, impersonation, and virtual balance transfers.
- CVE-2026-111489Critical
A static credential embedded in the MatchPoint mobile app has been reported to return the 'autorizado' token. The report states that this token grants unauthenticated access to API services.
- CVE-2026-85076Critical
Prior to 0.9.124, an authenticated non-admin with run_events, create_events, or edit_events privilege in Cronicle can supply undeclared keys in event params through api_create_event, api_update_event, or api_run_event. A key colliding with a security-sensitive environment variable can override the plugin execution context, potentially causing privilege escalation, arbitrary code execution, data access, or service disruption.
- CVE-2026-48705Critical
Prior to 1.6.1, MONAI's PydicomReader._get_affine() trusts non-finite values in DICOM PixelSpacing, ImagePositionPatient, and ImageOrientationPatient fields and composes them into an affine matrix without validation. An unauthenticated attacker who can upload a crafted DICOM to a default MONAILabel deployment can propagate NaN or infinity values, causing inference failures, persistent datastore poisoning, or geometrically corrupted results.
- CVE-2026-46350Critical
Prior to 0.52.0, dcmjs's DecimalString and IntegerString implementations in src/ValueRepresentation.js sanitize text with a permissive regular expression and pass the result to JavaScript's Number constructor without validating finiteness or DICOM rules. Scientific notation overflow in a DS or IS field can produce Infinity or NaN, and IntegerString accepts exponent notation and values outside the signed 32-bit IS range. Applications trusting these values can propagate invalid numbers into geometry, windowing, dose scaling, and volume reconstruction.
Original NVD description (English source)
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().
Vulnerability data from NVD (NIST) · CISA KEV · EPSS

