Description
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.
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 4.0 | linux-2.6 | 2.6.18.dfsg.1-18etch3 | DSA-1565-1 |
Red Hat
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| RHEL 5 | kernel +12 | 2.6.18-92.1.10.el5 | RHSA-2008:0612 |
Advisories 2
- RHSA-2008:0612 Red Hat Security Advisory: kernel security and bug fix update Red Hat Security Advisories (RHSA) · Jun 26, 2026
- DSA-1565-1 linux-2.6 - several vulnerabilities Debian Security (DSA / DLA) · Mar 9, 2026
References
- http://bugs.gentoo.org/show_bug.cgi?id=215000
- USN-618-1 vendor-advisory
- 31341 third-party-advisory
- DSA-1565 vendor-advisory
- oval:org.mitre.oval:def:10974 vdb-entry signature
- 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
- RHSA-2008:0612 vendor-advisory
- 30769 third-party-advisory
- 30018 third-party-advisory
- linux-kernel-rlimitcpu-security-bypass(42145) vdb-entry