Bug ID 755977: Missing check for NULL condition causes tmm crash.

Last Modified: Jan 16, 2024

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

Known Affected Versions:
12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3

Fixed In:
15.0.0, 14.1.3.1, 13.1.3.4, 12.1.5

Opened: Jan 18, 2019

Severity: 3-Major

Symptoms

Missing check for NULL condition causes tmm crash.

Impact

Traffic disrupted while tmm restarts.

Conditions

This issue occurs when all of the following conditions are met: 1) The BIG-IP system receives a new connection request and attempts to select a pool member. 2) All pool members are unresponsive. This may be due to one of the following reasons: a) The pool members have reached their configured connection limit. b) There is no route to the pool members.

Workaround

None.

Fix Information

TMM correctly checks for NULL condition to prevent the crash.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips