Red Hat Enterprise Linux 10
Gdb: gdbserver: heap buffer overflow in cmd_qtdpsrc via qtdpsrc declared/actual length mismatch
A heap buffer overflow in gdbserver's QTDPsrc packet handler allows an unauthenticated remote attacker to achieve native code execution in the gdbserver process. The vulnerability results from a mismatch between a packet's declared source length and the actual data length, causing hex2bin to write beyond the allocated heap buffer.
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
There is no mitigation for this vulnerability. gdbserver has no authentication mechanism; exposure is limited only by network access to the gdbserver port. --- CME Mitigation Guidance (2026-11-06) --- 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 restrict network access and block exposure of gdbserver listening ports to untrusted networks: upgrade to the corresponding fixed Red Hat builds, which apply the documented input check, closing all 2 injection vectors (malformed QTDPsrc packet with declared length smaller than payload length, qGetTLSAddr packet to invoke corrupted function pointer). Until patched, this is a concern on Linux systems running gdbserver with reachable listening ports, so restrict network access to exposed gdbserver ports via firewalls or network filtering, as gdbserver has no built-in authentication. As a compensating measure, Enable ASLR to randomize memory layout and hinder predicting target addresses to overwrite function pointers, Run SELinux in enforcing mode to confine gdbserver to a least-privilege domain, Isolate gdbserver within dedicated user, PID, network, and mount namespaces to restrict post-compromise impact, and Drop unnecessary POSIX capabilities from the gdbserver process bounding set to restrict privilege. These controls limit blast radius and contain exploitation, but they do not fix the underlying heap buffer overflow defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-301 SELinux (Enforcing Mode) (medium)
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.