Last Modified: May 23, 2019
See more info
Known Affected Versions:
14.0.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 14.1.0, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168
Opened: Mar 07, 2019
TMSH does not correctly handle absence of input stream after closing interactive SSH session and remains active in an infinite loop using 100% CPU.
One CPU core is utilized in 100% by runaway TMSH process.
If TMSH is a process group leader, it will not be killed when the parent shell is terminated upon SSH session close. It is a rare case as TMSH would have to be deliberately promoted to a process group leader e.g. with setsid command. Usually the shell process is a group leader and, when it is terminated upon SSH session close, it will kill its child processes including TMSH.
TMSH should not be intentionally promoted to a process group leader. Abandoned TMSH process can be safely killed with "killall tmsh" command.