Bug ID 1519001: After a crash, tmm may experience memory corruption

Last Modified: May 29, 2024

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

Known Affected Versions:
14.1.5.6, 17.1.1.2, 17.1.1.3

Opened: Feb 13, 2024

Severity: 2-Critical

Symptoms

On an F5OS tenant using the sep driver, if tmm does not stop gracefully - meaning it crashed or was killed, it may experience memory corruption when it starts again, leading to another crash.

Impact

Tmm may crash again when it starts up. Traffic disrupted while tmm restarts.

Conditions

-- F5OS tenant -- Tmm does not shut down gracefully r4000 and r2000 series appliances are not affected.

Workaround

Reboot the tenant, or if tmm is able to start, shut down tmm gracefully and restart.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips