Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
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.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3
Fixed In:
11.6.1 HF2, 11.5.4 HF3
Opened: Jun 08, 2016 Severity: 2-Critical Related Article:
K82090640
Use after free or double-free of the nexthop object may cause memory corruption or TMM core.
The BIG-IP dataplane might crash. This is a very timing/memory-usage-dependent issue.
This can happen if the server-side connection establishment takes some time to complete, creating a large enough time window where the nexthop object might be freed.
None.
Management of nexthop object reference counting is more consistent.