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.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Link | Tags |
---|---|
http://bugs.gentoo.org/show_bug.cgi?id=215000 | |
http://www.ubuntu.com/usn/usn-618-1 | vendor advisory |
http://secunia.com/advisories/31341 | third party advisory |
http://www.debian.org/security/2008/dsa-1565 | vendor advisory |
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10974 | vdb entry signature |
http://www.securityfocus.com/bid/29004 | vdb entry |
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git%3Ba=commitdiff%3Bh=9926e4c74300c4b31dee007298c6475d33369df0 | |
http://kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.22 | |
http://www.redhat.com/support/errata/RHSA-2008-0612.html | vendor advisory |
http://secunia.com/advisories/30769 | third party advisory |
http://secunia.com/advisories/30018 | third party advisory |
https://exchange.xforce.ibmcloud.com/vulnerabilities/42145 | vdb entry |