CVE-2026-89092
Description
A flaw was found in glibc, specifically within the nscd service. A remote attacker, operating a malicious Domain Name System (DNS) server, could send an overly large DNS response. This could trigger a stack overflow in the nscd service, causing it to crash and leading to degraded DNS resolution for the system. There is also a remote possibility of nscd cache corruption.
Statement
A flaw of moderate impact was found in the nscd service of the GNU C Library (glibc), as shipped in Red Hat Enterprise Linux and in the Red Hat OpenShift Container Platform core images that embed RHEL components. A remote attacker controlling a malicious or compromised DNS server used by a system with nscd enabled could return an overly large DNS response to a query, triggering a stack overflow in an nscd thread that crashes the service and degrades DNS name resolution for the system. Exploitation requires an adjacent network position and is difficult in practice: the attacker must operate the DNS server the victim uses for name resolution, and that server must be capable of processing DNS records large enough to overflow an nscd thread stack. There is also a remote possibility of nscd cache corruption. In typical installations nscd runs in an isolated context as its own user without a shell, which limits the impact of any compromise, and a crash causes performance degradation when resolving names rather than a denial of service of the whole system. The Red Hat severity (Moderate, CVSS 4.2, CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L) is aligned with the upstream glibc advisory. For most affected Red Hat Enterprise Linux and OpenShift Container Platform streams the fix is deferred because the issue is rated Moderate with a CVSS score below the threshold that warrants active remediation, leaving the residual risk that affected systems with nscd enabled and relying on an untrusted DNS server could experience repeated nscd crashes and degraded name resolution. A fix is being pursued for the remaining delegated affected streams, while certain newer streams were assessed as not affected.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 4.2 | N/A | 4.2 |
| Attack Vector | Adjacent Network | N/A | Adjacent Network |
| Attack Complexity | High | N/A | High |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | Low | N/A | Low |
| Availability Impact | Low | N/A | Low |
Vector
Red Hat: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
cve.org: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
Buffer overflows often can be used to execute arbitrary code, which is usually outside the scope of the product's implicit security policy. This can often be used to subvert any other security service.
Availability
Technical Impact: Modify Memory; DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU)
Buffer overflows generally lead to crashes. Other attacks leading to lack of availability are possible, including putting the product into an infinite loop.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.