CVE-2026-134657 in oai-cn5g-pcfinfo

Summary

by MITRE • 11/22/2026

OpenAirInterface CN5G PCF through 2.2.2 contains a memory leak vulnerability in pcf_smpc::delete_sm_policy_handler() that leaves stale UE IPv4, SUPI and DNN index entries after association deletion. Attackers can trigger repeated SM policy create and delete cycles over N7 via PDU session establishment and release to grow PCF memory without bound and break association lookups.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 11/22/2026

The vulnerability identified in OpenAirInterface CN5G Policy Control Function (PCF) versions up to 2.2.2 represents a critical resource exhaustion flaw rooted in improper memory management within the session management policy handling logic. Specifically, the defect resides in the pcf_smpc::delete_sm_policy_handler() function, which is responsible for cleaning up resources associated with User Equipment (UE) sessions when they are terminated. Under normal operational conditions, this handler should release all allocated data structures and clear references to UE-specific identifiers upon association deletion. However, due to a coding error or incomplete cleanup routine, the system fails to properly deallocate memory entries corresponding to stale UE IPv4 addresses, Subscription Permanent Identifiers (SUPI), and Data Network Name (DNN) indices. This oversight results in these data structures persisting in memory even after the logical association between the network function and the user equipment has been severed, creating a classic case of resource leakage that degrades system stability over time.

From an operational perspective, this vulnerability allows for significant denial-of-service impacts through automated exploitation techniques. An attacker with access to the N7 interface, which facilitates communication between the Session Management Function (SMF) and the PCF in 5G core networks, can trigger a continuous cycle of session creation and deletion requests. By repeatedly initiating PDU session establishment followed immediately by release procedures, an adversary forces the PCF to allocate new memory for each incoming request while failing to reclaim it during the teardown phase. This unbounded growth in memory consumption eventually exhausts available system resources on the host running the PCF service. As memory fills up, the performance of the policy control function degrades severely, leading to increased latency in policy decisions or complete service failure as the application becomes unable to process new legitimate requests due to lack of heap space.

The security implications extend beyond simple resource exhaustion. The persistence of stale UE IPv4 addresses and SUPI entries can disrupt association lookups within the PCF database. When subsequent valid sessions attempt to query existing policies, the presence of corrupted or orphaned index entries may cause lookup failures, incorrect policy application, or unexpected termination of active connections for legitimate users. This undermines the reliability and integrity of the 5G core network's control plane operations. Furthermore, such memory corruption patterns can sometimes serve as a precursor to more severe exploits if the leaked pointers are later dereferenced in an unintended context, although the primary impact here is availability-related rather than confidentiality or integrity compromise directly through code execution.

This vulnerability aligns with Common Weakness Enumeration (CWE) category CWE-401, which describes missing release of memory after effective lifetime, and also relates to CWE-772, where insufficient cleanup occurs upon object removal. In terms of the MITRE ATT&CK framework for Enterprise, this behavior is consistent with techniques used in resource exhaustion attacks aimed at disrupting service availability rather than gaining unauthorized access or data exfiltration. The attack vector leverages legitimate protocol interactions over N7, making it difficult to distinguish from normal traffic without deep packet inspection and behavioral analysis of memory usage patterns on the PCF host.

Mitigation strategies should focus primarily on applying vendor-provided patches that address the specific logic error in pcf_smpc::delete_sm_policy_handler(). For organizations unable to immediately patch their infrastructure, implementing strict rate limiting policies on N7 interface traffic can help mitigate the speed at which memory is consumed during such abuse cycles. Additionally, deploying monitoring solutions that track PCF process memory usage and alert on anomalous growth rates can provide early warning of potential exploitation attempts. Network segmentation restricting access to the N7 interface only to authorized SMFs reduces the attack surface available to external adversaries. Regular auditing of session lifecycle management code in 5G core components is essential to prevent similar resource leakage defects from persisting in production environments, ensuring long-term stability and security of critical telecommunications infrastructure.

Responsible

VulnCheck

Reservation

11/22/2026

Disclosure

11/22/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Do you want to use VulDB in your project?

Use the official API to access entries easily!