PoC Monitor
← All CVEs
CVE-2026-121995published 5 Nov 2026 16:08 UTCData: JSON · API

Red Hat Enterprise Linux 10

Gdb: gdb: stack buffer overflow in parse_tracepoint_definition via stale rs->buf tail

A stack buffer overflow in the GDB client's tracepoint upload handler allows an attacker-controlled debug stub to corrupt stack memory automatically during connection setup. The overflow results from GDB reading beyond the current reply boundary into a stale prior reply in the shared packet buffer.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.5high · scored by CNA · CWE-121
CISA KEV Not listednot known exploited

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. Users should only connect GDB to trusted debug targets. --- 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 GDB remote debugging sessions to trusted remote stubs and prevent connections to untrusted endpoints: upgrade to the corresponding fixed Red Hat builds, which apply the documented input check, closing crafted qTsP remote debug response following a longer qTfP response. Until patched, this is a concern on Linux systems running GDB remote debugging sessions connecting to remote debug targets, so Only initiate target remote debugging sessions to verified, trusted debug stubs and targets. As a compensating measure, Run SELinux in enforcing mode to confine GDB execution under mandatory access control and limit the blast radius of memory corruption. These controls limit blast radius and contain exploitation, but they do not fix the underlying stack buffer overflow defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-301 SELinux (Enforcing Mode) (medium)

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published5 Nov 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.