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

Published Nov 3, 2026
·
Updated

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.

Other sources

Stack buffer overflow in parsetracepointdefinition (gdb/tracepoint.c), Z branch. The packet buffer rs->buf is reused between requests without clearing. When a short qTsP reply follows a longer qTfP reply, the parser's p pointer — advanced through strchr/unpackvarlenhex calls — walks past the short reply's NUL terminator into stale data from the prior longer reply. hex2bin then copies strlen(p)/2 pairs into an alloca buffer sized only for the short reply, overflowing it. Fires automatically during target remote connection setup with no additional user commands.

— Red Hat

Affected Software

0 affected components

Event History

Nov 3, 2026
Data Sourced
via Red Hat·10:03 AM
DescriptionSeverityAffected Software
Nov 5, 2026
CVE Published
via MITRE·04:08 PM
Data Sourced
via MITRE·04:08 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:18 PM
DescriptionSeverityWeakness

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203