Bug ID 514604: Nexthop object can be freed while still referenced by another structure

Last Modified: Jul 18, 2026

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

Known Affected Versions:
11.5.1, 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, 11.5.2 hf1, 11.5.3, 11.5.3 hf1, 11.5.3 hf2, 11.5.4, 11.5.4 hf1, 11.5.4 hf2, 11.5.4 hf3, 11.5.4 hf4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.0 hf1, 11.6.0 hf2, 11.6.0 hf3, 11.6.0 hf4, 11.6.0 hf5, 11.6.0 hf6, 11.6.0 hf7, 11.6.0 hf8, 11.6.1, 11.6.1 hf1, 11.6.1 hf2

Fixed In:
12.0.0, 11.6.2

Opened: Mar 26, 2015

Severity: 3-Major

Related Article: K17467

Symptoms

Use after free of the Nexthop object may cause memory corruption or tmm core.

Impact

The BIG-IP system might crash. This is a very timing/memory-usage dependent issue that is rarely encountered.

Conditions

This can happen if the proxy connection takes some time to complete, creating a large enough time window where the nexthop object might be freed.

Workaround

None.

Fix Information

Management of nexthop object reference counting is more consistent.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips