kernel: setrlimit(RLIMIT_CPUINFO) with zero value doesn't inherit properly across children
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 5 | |||
| kernel-0:2.6.18-92.1.10.el5 | cpe:/o:redhat:enterprise_linux:5 | RHSA-2008:0612 | 2008-08-04T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-1565-1 | New Linux 2.6.18 packages fix several vulnerabilities |
EUVD |
EUVD-2008-1301 | 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. |
Ubuntu USN |
USN-618-1 | Linux kernel vulnerabilities |
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.506% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.