Last Modified: Jun 11, 2026
Affected Product(s):
BIG-IP PEM
Known Affected Versions:
17.5.1.3, 17.5.1.4, 17.5.1.5, 17.5.1.6
Opened: Apr 18, 2026 Severity: 3-Major
GGx sessions remain even after the deletion of PEM sessions. The memory allocated to Gx sessions remains intact. As more PEM sessions are created and deleted, the memory for Gx sessions continues to grow and is not released.
A slight increase in memory due to Gx sessions persisting even after PEM session deletion may lead to consequences over time, such as memory shortages.
This is a rare timing-based scenario in which the diam_app is busy sending requests to a non-responsive PCRF. As a result, the middleware (MW) message bus becomes full. When this happens, the notification from SPM to Gx to end the Gx session is dropped because the MW bus has reached its capacity.
None
None