kernel: oom_badness() integer overflow
Published May 17, 2012
5.5
MEDIUMCVSS 3.1
EPSS 0.45%
Description
Integer overflow in the oom_badness function in mm/oom_kill.c in the Linux kernel before 3.1.8 on 64-bit platforms allows local users to cause a denial of service (memory consumption or process termination) by using a certain large amount of memory.
Affected products
No data.
Configuration 1
- < 3.1.8
Configuration 2
- 6.0
No data.
Red Hat Enterprise MRG 2
kernel-rt-0:3.0.18-rt34.53.el6rt
Fixed · RHSA-2012:0333
Red Hat Enterprise Linux 4
kernel
Not affected
Red Hat Enterprise Linux 5
kernel
Not affected
Red Hat Enterprise Linux 6
kernel
Affected
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise MRG 2 | kernel-rt-0:3.0.18-rt34.53.el6rt | Fixed | RHSA-2012:0333 |
| Red Hat Enterprise Linux 4 | kernel | Not affected | n/a |
| Red Hat Enterprise Linux 5 | kernel | Not affected | n/a |
| Red Hat Enterprise Linux 6 | kernel | Affected | n/a |
No package ranges for this CVE.
Remediation
Red Hat statement
This issue did not affect the Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, and 6 as they did not backport the upstream commit f755a04 that introduced this. This has been addressed in Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2012-0333.html.
Metrics
No CVSS v4.0 score for this CVE.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
No CVSS v3.0 score for this CVE.
AV:L/AC:L/Au:N/C:N/I:N/A:C
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 1, 2026.
Score over time
2022–2026- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Percentile over time
- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Table of values (12 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 1, 2026 | 0.45% (0.00453) | 37.01th | v5 (v2026.06.15) |
| Jun 15, 2026 | 0.46% (0.00457) | 35.99th | v5 (v2026.06.15) |
| Mar 17, 2025 | 0.06% (0.00056) | 14.84th | v4 (v2025.03.14) |
| Dec 12, 2024 | 0.04% (0.00043) | 11.63th | v3 (v2023.03.01) |
| Jun 20, 2024 | 0.04% (0.00043) | 9.83th | v3 (v2023.03.01) |
| Mar 7, 2023 | 0.04% (0.00043) | 7.83th | v3 (v2023.03.01) |
| Mar 6, 2023 | 0.95% (0.00950) | 32.28th | v2 (v2022.01.01) |
| Feb 13, 2023 | 0.95% (0.00950) | 31.86th | v2 (v2022.01.01) |
| Feb 3, 2023 | 1.03% (0.01034) | 40.96th | v2 (v2022.01.01) |
| Sep 10, 2022 | 0.95% (0.00950) | 30.63th | v2 (v2022.01.01) |
| Apr 1, 2022 | 0.95% (0.00950) | 28.61th | v2 (v2022.01.01) |
| Feb 4, 2022 | 0.95% (0.00950) | 13.46th | v2 (v2022.01.01) |
References (7)
- http://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.1.8 x_refsource_CONFIRMPatchVendor Advisory
- http://www.openwall.com/lists/oss-security/2011/11/01/2 mailing-listx_refsource_MLISTExploitMailing ListThird Party Advisory
- https://access.redhat.com/security/cve/CVE-2011-4097 Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=750399 x_refsource_CONFIRMExploitIssue TrackingPatchThird Party Advisory
- https://github.com/torvalds/linux/commit/56c6a8a4aadca809e04276eabe5552935c51387f x_refsource_CONFIRMExploitPatchThird Party Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2011-4097
- https://www.cve.org/CVERecord?id=CVE-2011-4097
| Link | Providers | Tags |
|---|---|---|
| http://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.1.8 | x_refsource_CONFIRMPatchVendor Advisory | |
| http://www.openwall.com/lists/oss-security/2011/11/01/2 | mailing-listx_refsource_MLISTExploitMailing ListThird Party Advisory | |
| https://access.redhat.com/security/cve/CVE-2011-4097 | Vendor Advisory | |
| https://bugzilla.redhat.com/show_bug.cgi?id=750399 | x_refsource_CONFIRMExploitIssue TrackingPatchThird Party Advisory | |
| https://github.com/torvalds/linux/commit/56c6a8a4aadca809e04276eabe5552935c51387f | x_refsource_CONFIRMExploitPatchThird Party Advisory | |
| https://nvd.nist.gov/vuln/detail/CVE-2011-4097 | ||
| https://www.cve.org/CVERecord?id=CVE-2011-4097 |
Change history (0)
No recorded changes yet.