CVE-2026-99212 is a high-severity vulnerability in the Linux kernel's RDS (Reliable Datagram Sockets) RDMA connection management. It involves improper handling of RDMA connection IDs on route failure, where an ID that RDS still owns can be prematurely destroyed, leading to use-after-free conditions. This flaw was fixed by ensuring the connection ID remains owned by RDS until proper shutdown, preventing premature destruction.
A vulnerability in the Linux kernel's RDS RDMA CM event handler allows a kernel crash due to an uninitialized pointer dereference when handling connection requests on non-InfiniBand RDMA devices such as iWARP RNICs. This occurs because the transport pointer is not initialized for non-IB devices, leading to a NULL dereference and kernel oops. The issue has been fixed by initializing the transport pointer explicitly, rejecting connection requests on non-IB devices, and dropping connections that resolve to non-IB devices before route resolution.
A vulnerability in filelock's ReadWriteLock and AsyncReadWriteLock components allows a local user with write permission on the lock database's parent directory to rename directories and cause the lock user's process to recursively delete arbitrary directories. This occurs because the lock cleanup does not verify that the directory it deletes is still the originally created lock directory, enabling deletion of directories renamed onto the expected lock directory name. The issue affects filelock versions 4.1.0 through 4.2.0 on macOS and POSIX systems without a usable /proc/self/fd, such as containers or chroots without /proc. The vulnerability requires a non-sticky, writable shared parent directory and local user privileges. The CVSS 3.1 score is 6.1 (Medium).
boneIO Black firmware ships with authentication disabled by default. Its management web API listens on all network interfaces and exposes all endpoints without requiring credentials. An unauthenticated remote attacker can fully control the device, causing denial of service, modifying configuration, and operating connected physical circuits.
This issue was fixed in version 1.6.0: a device without an administrator account refuses API requests until the owner creates one in the first-run wizard, and every API route is restricted to an authenticated role.
Versions before 1.2.0 are based on Debian 10, are no longer supported and cannot be upgraded in place; affected devices should be re-flashed with the 1.6.0 system image.
Kameleo versions 5.0.1.0 through 5.0.1.19 contain a server-side request forgery (SSRF) vulnerability in the InternalController.TestProxy function within the Proxy Validation component. This vulnerability allows remote attackers to manipulate host and port arguments to induce the server to make unintended requests. The issue is addressed in version 5.2.0, where the vulnerable route was removed and replaced.
CVE-2026-101259 is a vulnerability in the Apache Camel CoAP component affecting versions from 4.0.0 before 4.18.5 and from 4.19.0 before 4.22.2. It allows generation of error messages containing sensitive information such as class names, file paths, hostnames, and connection details in the payload of 5.00 Internal Server Error responses. This occurs when the CoAP consumer fails to build its response after route completion, exposing internal deployment details to remote clients. The issue is fixed in Apache Camel versions 4.18.5, 4.22.2, and 4.23.0. Users are advised to upgrade to these versions or apply recommended mitigations if immediate upgrade is not possible.
Starman versions prior to 0.4019 for Perl contain a vulnerability where specially crafted chunked HTTP request bodies can cause CPU exhaustion due to quadratic regex backtracking. This occurs because the regex used to parse chunk-size lines does not properly handle lines with a bare LF followed by CRLF, leading to excessive backtracking and high CPU usage. An attacker can exploit this by sending such requests to any route, causing denial of service through resource exhaustion.
Echo versions prior to v4.16.1 and v5.4.1 contain a vulnerability where rejected WebSocket upgrade requests can bypass route-level access controls. This occurs because Echo's proxy middleware forwards subsequent HTTP requests on a connection with a rejected upgrade directly to the upstream without passing through Echo's router or middleware, potentially bypassing authentication or authorization enforced at Echo routes. Exploitation requires an accessible proxy route, an upstream that rejects the upgrade without closing the connection, and a target resource on that upstream without its own authorization. Fixed in versions v4.16.1 and v5.4.1.
Kruize Autotune's REST API lacks an authentication layer, exposing sensitive datasource configuration endpoints that return authentication secrets in cleartext. This allows any client with network access to the service to retrieve credentials such as basic-auth passwords, bearer tokens, API keys, and OAuth2 client secrets. The vulnerability is tied to the network exposure of the service, which is often exposed via NodePort, LoadBalancer, or OpenShift Route configurations. The issue was fixed in version 0.11.2 by excluding sensitive fields from API responses and tightening CORS policies. However, credentials remain stored in cleartext at rest, which is a separate concern.
A vulnerability in the Linux kernel's IPv6 UDP handling allows off-path attackers to conduct side-channel attacks on the IPv6 exception cache to discover ephemeral UDP ports. The issue arises because exceptions are only created in the cache if a matching socket is found, enabling attackers to infer port usage. The vulnerability has been addressed by changing the kernel to always create exceptions before socket matching, preventing this side-channel. This fix may cause additional route lookups and exceptions but does not introduce new exception creation capabilities beyond previous behavior.
A vulnerability in the Linux kernel's IPv4 routing notification mechanism could cause a null pointer dereference when a nexthop group shrinks during route notification sizing. This occurs because the code does not properly handle the case where the nexthop group has fewer paths after an update, leading to a potential crash or instability. The issue has been resolved by stopping the sizing process when the indexed path is absent.
This vulnerability in the Linux kernel concerns a warning triggered by a race condition in route notification size handling. The issue arises when asynchronous route notifications for hardware flag changes are processed, potentially causing a legitimate size error that was previously misinterpreted as a bug. The fix removes the warning while maintaining error handling and notification to listeners.
A Linux kernel vulnerability related to IPv6 route notification size warnings has been addressed. The issue involves a race condition in fib6_info_hw_flags_set() where skb sizing and filling operations can mismatch due to concurrent changes, causing incorrect warnings. The fix removes the misleading warning while preserving error handling.
A vulnerability in the Linux kernel's ip6_gre module related to obsolete ERSPAN Path MTU (PMTU) update handling has been resolved. The legacy PMTU update code in ip6erspan_tunnel_xmit() incorrectly dereferences a null pointer due to treating a metadata destination as a route without an output device, causing a kernel panic. This issue was triggered by specific user and network namespace configurations. The obsolete code was removed to align ERSPAN PMTU handling with IPv6 GRE, eliminating the null pointer dereference and preventing kernel crashes.
A vulnerability in the Linux kernel's IPv6 Segment Routing (SR) implementation was resolved by ensuring the use of skb_get_hash_net() in the seg6_make_flowlabel() function. The issue arose because __skb_flow_dissect() requires a network namespace pointer, which was not always correctly provided when skb->dev and skb->sk were unset. This could occur in scenarios such as a TIPC UDP bearer sending discovery messages through an IPv4 route using seg6 encapsulation with seg6_flowlabel enabled. The fix ensures the correct net pointer is used to avoid potential kernel issues.
CVE-2026-99077 is a vulnerability in the Linux kernel's IPv4 UDP implementation where the creation of FIB nexthop exceptions (FNHE) occurs only after matching a UDP socket. This allows off-path attackers to perform side-channel attacks to discover ephemeral UDP ports by observing the FNHE cache. The vulnerability is mitigated by always creating FNHEs before socket matching, ensuring that attacker guesses result in cache updates that do not reveal socket information. The fix introduces additional route lookups and may create multiple exceptions for the same destination IP in some cases.