CVE-2026-121997

Gdb: gdbserver: heap buffer overflow in cmd_qtdpsrc via qtdpsrc declared/actual length mismatch

  • High 8.1

Description

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.

Key facts

Published
5 Nov 2026
Last changed
6 Nov 2026
Assigned by
redhat
EPSS
0.71% likely to be exploited in the next 30 days, higher than 54.107% 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.

  • 8.1CVSS 3.1, Highfrom the CNA (redhat)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

What to do

  • 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 uCNA 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.

CNA context is abbreviated; consult the original record for the complete statements.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Enterprise Linux 10
  • Default status: unaffected
Red HatRed Hat Enterprise Linux 10
  • Default status: affected
Red HatRed Hat Enterprise Linux 6
  • Default status: affected
Red HatRed Hat Enterprise Linux 7
  • Default status: affected
Red HatRed Hat Enterprise Linux 8
  • Default status: unaffected
Red HatRed Hat Enterprise Linux 8
  • Default status: affected
Red HatRed Hat Enterprise Linux 8
  • Default status: affected
Red HatRed Hat Enterprise Linux 8
  • Default status: affected
Red HatRed Hat Enterprise Linux 9
  • Default status: unaffected
Red HatRed Hat Enterprise Linux 9
  • Default status: affected
Red HatRed Hat Hardened Images
  • Default status: affected

Timeline

  1. 21 Oct 2026 Reported to Red Hat.
  2. 5 Nov 2026 Made public.
  3. 5 Nov 2026 Published

Weakness

References