Public vulnerability disclosure

CVE-2026-121995

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

publishedCWE-121

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.

Technical severity7.5 highCVSS 3.1 · CNA: redhat
Published2026-11-05Source updated 2026-11-06
Collected2026-11-063 attributed sources

Fixes and workarounds

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)

Source: CNA: redhat

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
Red Hat Enterprise Linux 10
Red Hat
crash
https://access.redhat.com/downloads/content/package-browser/
Range not reported
Other versions: unaffected
CNA: redhat
Red Hat Enterprise Linux 10
Red Hat
gdb
https://access.redhat.com/downloads/content/package-browser/
Range not reported
Other versions: affected
CNA: redhat
Red Hat Enterprise Linux 6
Red Hat
gdb
https://access.redhat.com/downloads/content/package-browser/
Range not reported
Other versions: affected
CNA: redhat
Red Hat Enterprise Linux 7
Red Hat
gdb
https://access.redhat.com/downloads/content/package-browser/
Range not reported
Other versions: affected
CNA: redhat
Red Hat Enterprise Linux 8
Red Hat
crash
https://access.redhat.com/downloads/content/package-browser/
Range not reported
Other versions: unaffected
CNA: redhat
Red Hat Enterprise Linux 8
Red Hat
gcc-toolset-14-gdb
https://access.redhat.com/downloads/content/package-browser/
Range not reported
Other versions: affected
CNA: redhat
Red Hat Enterprise Linux 8
Red Hat
gcc-toolset-15-gdb
https://access.redhat.com/downloads/content/package-browser/
Range not reported
Other versions: affected
CNA: redhat
Red Hat Enterprise Linux 8
Red Hat
gdb
https://access.redhat.com/downloads/content/package-browser/
Range not reported
Other versions: affected
CNA: redhat
Red Hat Enterprise Linux 9
Red Hat
crash
https://access.redhat.com/downloads/content/package-browser/
Range not reported
Other versions: unaffected
CNA: redhat
Red Hat Enterprise Linux 9
Red Hat
gdb
https://access.redhat.com/downloads/content/package-browser/
Range not reported
Other versions: affected
CNA: redhat
Red Hat Hardened Images
Red Hat
gdb
https://access.redhat.com/downloads/content/package-browser/
Range not reported
Other versions: affected
CNA: redhat

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 7.5
high
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HCNA: redhat
3.1 / 7.5
high
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HNVD: [email protected]

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide