Bug ID 454018: Nexthop to tmm0 ref-count leakage could cause TMM core

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
11.1.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 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.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1

Fixed In:
11.6.0, 11.5.3 HF2, 11.4.1 HF10, 11.2.1 HF11

Opened: Mar 26, 2014
Severity: 3-Major
Related Article:


Each use of the interface tmm0 for inter-TMM communication is supposed to increment its count of nexthop references. When the use of the interface is expired, the reference count is supposed to decrement, but in this case, the reference count is not decremented.


Reference count leaks, which causes the count to monotonically increase, which eventually might cause TMM to crash and restart.


This occurs when TMM runs over an extended period of time, and internal communication between TMMs over tmm0 is heavy during the period.


This issue has no workaround.

Fix Information

The nexthop reference count of the interface tmm0 is thoroughly examined and corrected, so it no longer leaks ref counts.

Behavior Change