CVE-2025-54805

When an iRule is configured on a virtual server via the declarative API, upon re-instantiation, the cleanup process can cause an increase in the Traffic Management Microkernel (TMM) memory resource utilization.  Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
References
Link Resource
https://my.f5.com/manage/s/article/K000151596 Vendor Advisory
Configurations

Configuration 1 (hide)

OR cpe:2.3:a:f5:big-ip_next_cloud-native_network_functions:*:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_next_for_kubernetes:2.0.0:*:*:*:*:*:*:*
cpe:2.3:a:f5:big-ip_next_service_proxy_for_kubernetes:*:*:*:*:*:*:*:*

History

18 Oct 2026, 21:10

Type Values Removed Values Added
Summary
  • (es) Cuando se configura un iRule en un servidor virtual a través de la API declarativa, tras la reinstanciación, el proceso de limpieza puede causar un aumento en la utilización de los recursos de memoria del Microkernel de Gestión de Tráfico (TMM). Nota: Las versiones de software que han alcanzado el Fin de Soporte Técnico (EoTS) no se evalúan.

Information

Published : 2025-10-15 14:15

Updated : 2026-10-18 21:10


NVD link : CVE-2025-54805

Mitre link : CVE-2025-54805

CVE.ORG link : CVE-2025-54805


JSON object : View

Products Affected

f5

  • big-ip_next_service_proxy_for_kubernetes
  • big-ip_next_for_kubernetes
  • big-ip_next_cloud-native_network_functions
CWE
CWE-401

Missing Release of Memory after Effective Lifetime