Bug ID 903905: Default configuration of security mechanism causes memory leak in TMM

Last Modified: Jul 31, 2020

Bug Tracker

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

Known Affected Versions:
15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2

Fixed In:
16.0.0, 15.1.0.3

Opened: Apr 25, 2020
Severity: 2-Critical

Symptoms

Over time, memory is allocated by the TMM processes for use as 'xdata' buffers, yet this memory is never de-allocated; it is leaked and becomes unusable. Eventually a disruption of service occurs.

Impact

Traffic disrupted while tmm restarts.

Conditions

-- The BIG-IP system has been running for 8 weeks or longer without a system restart. -- The BIG-IP system's internal risk-policy subsystem (used by the security feature modules) has not been configured to communicate with an external risk-policy server. -- In a vCMP configuration, the BIG-IP 'host' instance is always susceptible, since no security features can be configured in its context.

Workaround

None.

Fix Information

Default configuration of security mechanism no longer causes memory leak in TMM.

Behavior Change