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

Last Modified: Sep 13, 2023

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

Known Affected Versions:
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 HF1, 11.5.3 HF1, 11.6.0, 11.6.1, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.2, 11.6.0 HF5, 11.5.3 HF2

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