Bug ID 497062: PEM configured with BWC doing PEM policy changes could trigger leak

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP PEM(all modules)

Known Affected Versions:
11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3

Fixed In:
12.0.0, 11.6.0 HF4

Opened: Dec 16, 2014
Severity: 3-Major
Related Article:


When PEM is configured to use bwc policy and cause re-evaluations due to pem policy change in configuration and/or PCRX could cause leak in bwc memory for active flows.


PEM configured with BWC doing PEM policy changes might trigger leak. Eventual low memory conditions, possibly followed by TMM core and traffic outage.


This occurs when the following conditions are met: PEM is configured to use BWC. -- System is processing active flows. -- PEM is applying a policy change event for live flows.


To work around this issue, complete the following steps: -- Restart tmm. -- Upgrade the image. -- Avoid PEM policy change events for live traffic flows. -- Attach BWC to the PEM policy after PEM policy change events.

Fix Information

The case in which the PEM policy is modified while the system is processing live traffic, PEM now initiates policy re-evaluation and BWC is attached correctly to the policy, so no memory leak occurs.

Behavior Change