Last Modified: Oct 11, 2026
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6, 16.1.6.1, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.1.3.1, 17.1.3.2, 17.1.3.4, 17.1.3.5, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3, 17.5.1.4, 17.5.1.5, 17.5.1.6, 17.5.1.8, 17.5.1.9
Opened: Mar 17, 2025 Severity: 3-Major
BGP process memory usage can grow over time when routes are repeatedly processed by route-maps that modify standard or extended communities.
The BGP process retains memory that should have been released. Repeated route processing can consume increasing amounts of system memory.
- A BGP route-map applies `set comm-list <list> delete` followed by a `set community` action, including `additive`, replacement, or `none`. At least one community remains after the deletion step. - Alternatively, a route-map action creates temporary extended communities before `set extcommunity rt` is applied (for example, `set extcommunity soo`). - Routes are repeatedly processed by that policy.
None
None