Bug ID 1388341: tmm crash upon context reference that was already released (HUDEVT_SHUTDOWN)

Last Modified: Nov 10, 2024

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

Known Affected Versions:
16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 17.0.0, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4

Fixed In:
16.1.5

Opened: Oct 24, 2023

Severity: 3-Major

Symptoms

While requests are delayed in TMM due to various reasons, their virtual server and BADOS profile might be deleted. This may lead to a TMM crash.

Impact

Traffic disrupted while tmm restarts.

Conditions

-- BIG-IP System, passing traffic. -- The virtual server has objects attached, such as complex iRules or BADOS, which cause the requests to take more time to get through the tmm. -- A connection is dropped while the request is still being handled.

Workaround

If possible, avoid using objects that cause requests to be delayed, such as iRules and behavioral DoS.

Fix Information

TMM does not crash when a connection is dropped while a request is still in the progress.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips