Cyber Resilience

CVE-2023-5156

Redhat Enterprise Linux 8.0 … 9.0

Published
25 September 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.013 68th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2023-5156 is a high-severity Missing Release of Memory after Effective Lifetime (CWE-401) vulnerability in Redhat Enterprise Linux. Its CVSS base score is 7.5 (High).

Operationally, ranked in the top 32% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

A flaw was found in the GNU C Library. A recent fix for CVE-2023-4806 introduced the potential for a memory leak, which may result in an application crash.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-4693Same product: Redhat Enterprise Linux
CVE-2023-7216Same product: Redhat Enterprise Linux
CVE-2023-4692Same product: Redhat Enterprise Linux
CVE-2023-7192Same product: Redhat Enterprise Linux
CVE-2024-5742Same product: Redhat Enterprise Linux
CVE-2025-32988Same product: Redhat Enterprise Linux
CVE-2025-32990Same product: Redhat Enterprise Linux
CVE-2026-5704Same product: Redhat Enterprise Linux
CVE-2026-4647Same product: Redhat Enterprise Linux
CVE-2026-6843Same product: Redhat Enterprise Linux

Affected Assets

gnu
glibc
2.34 — 2.39
redhat
enterprise linux
8.0, 9.0

Mitigating Controls

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce proper memory allocation/deallocation via coding standards, reviews, and tooling.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Security testing in development can detect unreleased memory, providing partial coverage of the weakness.

prevents

Secure development life cycle mandates memory-management practices that reduce missing-release defects.

prevents

Application security requirements can specify explicit memory-release rules, partially mitigating the weakness.

prevents

Secure system architecture and engineering principles include resource-management guidelines that address memory leaks.

prevents

Secure coding standards directly require proper allocation/deallocation, covering most of this weakness.

detects

Capacity management may detect memory exhaustion symptoms but does not prevent the coding flaw.

References