Red Hat Enterprise Linux 10
Libslirp: libslirp: out-of-bounds heap read in icmp_forward_error() leading to information disclosure
A flaw was found in libslirp in icmp_forward_error(). When building an ICMP error response, the length of the quoted original IPv4 packet was taken from the IP header without clamping it to the actual buffer length. A truncated or malformed packet could cause an out-of-bounds heap read, leaking host memory into the ICMP error packet returned to a guest or container.
Affected versions and mitigation
From the CVE record and the vendor's references.Mitigation
The record names no fix. Check the vendor advisory below.
Workaround
Red Hat is not aware of a practical temporary workaround that fully mitigates this issue or meets Red Hat Product Security's standards for usability, deployment, applicability, or stability. Customers are advised to apply the relevant security updates when/if they become available. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to clamp quoted IPv4 payload length to actual buffer bounds in libslirp icmp_forward_error before copying data into ICMP error responses: upgrade to the corresponding fixed Red Hat builds, which clamp s_ip_len to the source buffer length msrc->m_len before copying payload data into the ICMP error packet, closing crafted truncated IPv4 packets with ip_len exceeding mbuf length. Until patched, this is a concern on guests or containers transmitting network traffic through libslirp, so restrict untrusted guests or containers from transmitting network traffic across libslirp virtual network interfaces. These controls limit blast radius and contain exploitation, but they do not fix the underlying out-of-bounds heap read defect — apply the upstream patch to fully remediate.
References
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.