Last Modified: Sep 07, 2019
See more info
Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 13.1.1, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 14.0.0, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 14.0.1
Opened: Oct 01, 2018
If a tcl context is associated with a tmm-timer (while creating access session) using iRule, the timer object is removed during tcl context release but its association remains. When the timer fires, it tries to access a memory which is already freed, causing tmm to crash and generate a core.
Traffic disrupted while tmm restarts.
Creating access session using iRule.
There is no workaround at this time.
Now the timer object created under tcl context is tied with tcl command context and a callback function. This function will be called every time a tcl context is released. This will allow any additional cleanup (e.g. removal of timer from timer ring) and freeing the tcl command context.