CVE-2026-91141

Description

A flaw was found in vsomeip. A remote, unauthenticated attacker can cause a Denial of Service (DoS) by sending a specially crafted TCP packet containing an excessively large length field. This improper handling triggers disproportionate memory allocation, which can crash the service or lead to complete system memory exhaustion.

Statement

This vulnerability is rated as Important severity because an unauthenticated remote attacker can cause extensive memory starvation leading to process crashes or full host denial of service without needing credentials or prior privileges. While standard Red Hat Enterprise Linux releases do not include or activate vsomeip by default, specialized automotive and embedded installations that run SOME/IP communication over routable network interfaces are exposed. The risk is heightened in environments where vsomeip daemons are exposed to untrusted network segments, allowing low-volume traffic to exhaust target resources.

Mitigation

Restrict network exposure by limiting TCP access to the vsomeip communication ports to trusted hosts or internal interfaces using firewalld.

1. Allow access only from trusted source networks:
firewall-cmd --permanent --zone=internal --add-source=<trusted_subnet_or_ip>
firewall-cmd --permanent --zone=internal --add-port=<port>/tcp

2. Ensure vsomeip ports are not accessible from untrusted zones:
firewall-cmd --permanent --zone=public --remove-port=<port>/tcp

3. Apply firewall configuration:
firewall-cmd --reload

Caveats:
Restricting access to these ports blocks any unlisted electronic control units (ECUs) or endpoints from communicating with the SOME/IP daemon. Ensure all legitimate communicating nodes are added to the trusted source list.

Warning: Reloading firewall rules applies settings immediately and can disrupt existing active network connections.

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)

When allocating resources without limits, an attacker could prevent other systems, applications, or processes from accessing the same type of resource. It can be easy for an attacker to consume many resources by rapidly making many requests or causing larger resources to be used than is needed.

Frequently Asked Questions

Want to get errata notifications? Sign up here.