Descrizione
A stack buffer overflow in the GDB client's remote protocol handler allows an attacker-controlled debug target to execute arbitrary code in the GDB process. The vulnerability exists in fetch_register_using_p, which decodes a stub's register reply into an alloca-sized buffer without bounding writes by the register width.
Come correggere
Priorità: Media — correggere nel prossimo ciclo di patch. Motivazione: CVSS 8.8, EPSS 0.5% (percentile 42).
Versioni da aggiornare
Il record non riporta ancora i prodotti e le versioni corrette (analisi NVD in corso). Consultare l'advisory del vendor nei riferimenti.
Indicazioni del vendor
Workaround (testo originale del vendor):
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 enforce bounds checking against register size when decoding remote serial protocol register replies in the GDB client remote protocol handler: upgrade to the corresponding fixed Red Hat builds, which bounds RSP register reply decoding to the allocated register size rather than terminating only on NUL bytes, closing all 2 injection vectors (oversized RSP register reply, truncated RSP register reply stack disclosure). Until patched, this is a concern on Linux systems running GDB clients connecting to remote RSP debug targets, so Only connect the GDB client to known, trusted debug targets and avoid attaching to unverified or hostile remote RSP stubs. As a compensating measure, Enforce SELinux in enforcing mode to confine the actions of a compromised GDB process, Deploy an EDR agent to detect anomalous process behavior and post-exploitation payloads spawned from GDB, Monitor kernel syscall activity via eBPF to detect unexpected commands or shells spawned by the GDB…
Mitigazioni temporanee
Da applicare solo se non è possibile aggiornare subito:
- Ridurre la superficie esposta (disattivare servizi e funzionalità inutilizzati), mantenere attive le protezioni del sistema operativo (ASLR, DEP/NX) e segmentare la rete.
Verifica
- Individuare tutti gli asset con il prodotto interessato (inventario, scanner di vulnerabilità, CMDB).
- Confrontare la versione installata con quelle indicate sopra.
- Applicare l'aggiornamento in un ambiente di test, poi in produzione; riavviare i servizi se richiesto.
- Ripetere la scansione per confermare la correzione.