Last Modified: Oct 05, 2026
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
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, 21.1.0, 21.1.0.1, 21.1.0.2
Opened: Aug 25, 2026 Severity: 2-Critical
The Traffic Management Microkernel (TMM) may restart after the geolocation database is updated. This occurs while connections that were established before the update are still open
Traffic disrupted while TMM restarts
- A version 1 city geolocation database is installed - A FastL4 virtual server is configured with a TCP analytics profile that has the City or Postcode entity enabled - PVA acceleration is disabled on the FastL4 profile - Client connections are open when the geolocation database is updated
Disable the City and Postcode entities in the TCP analytics profile applied to the FastL4 virtual server. Alternatively, ensure no client connections are open when you update the geolocation database
None