CVE-2026-121995
Gdb: gdb: stack buffer overflow in parse_tracepoint_definition via stale rs->buf tail
- High 7.5
Description
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.
Key facts
- Published
- 5 Nov 2026
- Last changed
- 9 Nov 2026
- Assigned by
- redhat
- EPSS
- 0.293% likely to be exploited in the next 30 days, higher than 22.18% of CVEs (scores for 16 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: no; Technical impact: total
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 7.5CVSS 3.1, Highfrom the CNA (redhat)
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
What to do
- 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)CNA workaround statement
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Red Hat | Red Hat Enterprise Linux 10 |
|
| Red Hat | Red Hat Enterprise Linux 10 |
|
| Red Hat | Red Hat Enterprise Linux 6 |
|
| Red Hat | Red Hat Enterprise Linux 7 |
|
| Red Hat | Red Hat Enterprise Linux 8 |
|
| Red Hat | Red Hat Enterprise Linux 8 |
|
| Red Hat | Red Hat Enterprise Linux 8 |
|
| Red Hat | Red Hat Enterprise Linux 8 |
|
| Red Hat | Red Hat Enterprise Linux 9 |
|
| Red Hat | Red Hat Enterprise Linux 9 |
|
| Red Hat | Red Hat Hardened Images |
|
Timeline
- 21 Oct 2026 Reported to Red Hat.
- 5 Nov 2026 Made public.
- 5 Nov 2026 Published