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

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP PEM(all modules)

Known Affected Versions:
11.5.1 HF1, 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.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF4

Opened: Dec 20, 2014

Severity: 3-Major

Symptoms

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.

Impact

- memory leak.

Conditions

- PEM need to be configured to use bwc. - Active flows. - PEM policy change event for live flows.

Workaround

- restart tmm. - upgrade image. - avoid PEM policy change event for live traffic flows. - attach bwc to pem policy after PEM policy change event.

Fix Information

The case when PEM policy is modified on live traffic, PEM initiates policy re-evaluation. In process internally bwc is detached and attached. During this, the flow active flag is not cleared thus during flow release memory is not released.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips