Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

redhat логотип

CVE-2026-6791

Опубликовано: 10 авг. 2026
Источник: redhat
CVSS3: 5.9

Описание

When expanding paths that begin with a tilde () followed by a username, the internal parse_tilde function extracts the username to determine the user's home directory. The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash.

A flaw was found in glibc. When processing paths that start with a tilde (
) followed by a username, the wordexp function can be forced to allocate an excessive amount of memory on the program's stack. A remote attacker could exploit this by providing a very long username, leading to a stack exhaustion and causing a denial of service (DoS) for the affected application.

Затронутые пакеты

ПлатформаПакетСостояниеРекомендацияРелиз
Red Hat Enterprise Linux 6compat-glibcOut of support scope
Red Hat Enterprise Linux 6glibcOut of support scope
Red Hat Enterprise Linux 7compat-glibcFix deferred
Red Hat Enterprise Linux 7glibcFix deferred
Red Hat Hardened ImagesfilesystemNot affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-kserve-controller-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-kserve-llmisvc-controller-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-llama-stack-k8s-operator-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-model-serving-api-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbenches-operator-rhel9Not affected

Показывать по

Дополнительная информация

Статус:

Moderate
Дефект:
CWE-120
https://bugzilla.redhat.com/show_bug.cgi?id=2513603glibc: Glibc: Denial of Service via stack exhaustion during tilde expansion

5.9 Medium

CVSS3

Связанные уязвимости

ubuntu
3 месяца назад

When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user's home directory. The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash.

nvd
3 месяца назад

When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user's home directory. The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash.

msrc
3 месяца назад

Potential stack-based buffer clash during tilde expansion in wordexp

debian
3 месяца назад

When expanding paths that begin with a tilde (~) followed by a usernam ...

github
3 месяца назад

When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user's home directory. The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash.

5.9 Medium

CVSS3