This is old news, that keeps being reported over and over. Part of the problem, I suspect, is that people keep pointing to the wrong locus of the problem. Even here, this is being characterized as a Debian problem.

This is a kernel mechanism.

* https://nvd.nist.gov/vuln/detail/CVE-2013-6409

* https://nvd.nist.gov/vuln/detail/CVE-2015-6565

* https://nvd.nist.gov/vuln/detail/CVE-2016-2779

* https://nvd.nist.gov/vuln/detail/CVE-2016-7545

* https://nvd.nist.gov/vuln/detail/CVE-2017-5226

Some kernel people take the view that TIOCSTI is of no Earthly use, and there are other ways to implement line editing, and just make using it an error.

* http://undeadly.org/cgi?action=article&sid=20170701132619

* https://github.com/openbsd/src/commit/baecf150995d4609cd1479...

Others take a different view.

* http://www.openwall.com/lists/oss-security/2017/06/03/9

* http://www.openwall.com/lists/kernel-hardening/2017/05/15/8

* http://www.openwall.com/lists/kernel-hardening/2017/05/17/1

* http://www.openwall.com/lists/kernel-hardening/2017/05/29/16

* http://www.openwall.com/lists/kernel-hardening/2017/05/30/9

* http://www.openwall.com/lists/kernel-hardening/2017/05/30/26

* http://www.openwall.com/lists/kernel-hardening/2017/05/30/27

* http://www.openwall.com/lists/kernel-hardening/2017/05/30/32

* http://www.openwall.com/lists/kernel-hardening/2017/05/31/16