CVE-2025-61974

When a client SSL profile is configured on a virtual server, undisclosed requests can cause an increase in memory resource utilization. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Weakness

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

Affected Software

Name	Vendor	Start Version	End Version
Big-ip_next_cloud-native_network_functions	F5	1.1.0 (including)	1.4.1 (including)
Big-ip_next_cloud-native_network_functions	F5	2.0.0 (including)	2.1.0 (including)
Big-ip_next_for_kubernetes	F5	2.0.0 (including)	2.0.0 (including)
Big-ip_next_for_kubernetes	F5	2.1.0 (including)	2.1.0 (including)
Big-ip_next_service_proxy_for_kubernetes	F5	1.7.0 (including)	1.9.2 (including)
Big-ip_next_service_proxy_for_kubernetes	F5	2.0.0 (including)	2.0.2 (including)

Potential Mitigations

Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.
For example, glibc in Linux provides protection against free of invalid pointers.
When using Xcode to target OS X or iOS, enable automatic reference counting (ARC) [REF-391].
To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std::auto_ptr (defined by ISO/IEC ISO/IEC 14882:2003), std::shared_ptr and std::unique_ptr (specified by an upcoming revision of the C++ standard, informally referred to as C++ 1x), or equivalent solutions such as Boost.

References

https://my.f5.com/manage/s/article/K000156733

NVD	https://nvd.nist.gov/vuln/detail/CVE-2025-61974
CWE	https://cwe.mitre.org/data/definitions/401.html

Missing Release of Memory after Effective Lifetime

Weakness

Affected Software

Potential Mitigations

References