Linux kernel 2.6.17, and other versions before 2.6.22, does not check when a user attempts to set RLIMIT_CPU to 0 until after the change is made, which allows local users to bypass intended resource limits.
http://bugs.gentoo.org/show_bug.cgi?id=215000
http://kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.22
http://secunia.com/advisories/30018
http://secunia.com/advisories/30769
http://secunia.com/advisories/31341
http://www.debian.org/security/2008/dsa-1565
http://www.redhat.com/support/errata/RHSA-2008-0612.html
http://www.securityfocus.com/bid/29004
http://www.ubuntu.com/usn/usn-618-1
https://exchange.xforce.ibmcloud.com/vulnerabilities/42145
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10974