Vulnerabilities
Misconfiguration
Compliance
CVE Vulnerabilities

CVE-2014-3122

Uncontrolled Resource Consumption

Published: May 11, 2014 | Modified: Apr 12, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
4.9 MEDIUM
AV:L/AC:L/Au:N/C:N/I:N/A:C
RedHat/V2
4.9 MODERATE
AV:L/AC:L/Au:N/C:N/I:N/A:C
RedHat/V3
Ubuntu
MEDIUM
Vulnerability-free packages from our partners
root.io logo minimus.io logo echo.ai logo
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2014-3122
CWEhttps://cwe.mitre.org/data/definitions/400.html

The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings.

Weakness

The product does not properly control the allocation and maintenance of a limited resource.

Affected Software

NameVendorStart VersionEnd Version
Linux_kernelLinux*3.14.3 (excluding)
Red Hat Enterprise Linux 6RedHatkernel-0:2.6.32-504.el6*
Red Hat Enterprise MRG 2RedHatkernel-rt-0:3.10.33-rt32.34.el6rt*
LinuxUbuntuesm-infra-legacy/trusty*
LinuxUbuntulucid*
LinuxUbuntuprecise*
LinuxUbuntuprecise/esm*
LinuxUbuntuquantal*
LinuxUbuntusaucy*
LinuxUbuntutrusty*
LinuxUbuntutrusty/esm*
LinuxUbuntuupstream*
Linux-armadaxpUbuntuprecise*
Linux-armadaxpUbuntuquantal*
Linux-armadaxpUbuntuupstream*
Linux-awsUbuntuupstream*
Linux-ec2Ubuntulucid*
Linux-ec2Ubuntuupstream*
Linux-floUbuntutrusty*
Linux-floUbuntutrusty/esm*
Linux-floUbuntuupstream*
Linux-floUbuntuutopic*
Linux-floUbuntuvivid*
Linux-floUbuntuvivid/stable-phone-overlay*
Linux-floUbuntuwily*
Linux-floUbuntuxenial*
Linux-floUbuntuyakkety*
Linux-fsl-imx51Ubuntulucid*
Linux-fsl-imx51Ubuntuupstream*
Linux-gkeUbuntuupstream*
Linux-goldfishUbuntusaucy*
Linux-goldfishUbuntutrusty*
Linux-goldfishUbuntutrusty/esm*
Linux-goldfishUbuntuupstream*
Linux-goldfishUbuntuutopic*
Linux-goldfishUbuntuvivid*
Linux-goldfishUbuntuwily*
Linux-goldfishUbuntuxenial*
Linux-goldfishUbuntuyakkety*
Linux-goldfishUbuntuzesty*
Linux-grouperUbuntusaucy*
Linux-grouperUbuntutrusty*
Linux-grouperUbuntuupstream*
Linux-grouperUbuntuutopic*
Linux-hweUbuntuupstream*
Linux-hwe-edgeUbuntuupstream*
Linux-linaro-omapUbuntuprecise*
Linux-linaro-omapUbuntuquantal*
Linux-linaro-omapUbuntuupstream*
Linux-linaro-sharedUbuntuprecise*
Linux-linaro-sharedUbuntuquantal*
Linux-linaro-sharedUbuntuupstream*
Linux-linaro-vexpressUbuntuprecise*
Linux-linaro-vexpressUbuntuquantal*
Linux-linaro-vexpressUbuntuupstream*
Linux-lts-quantalUbuntuprecise*
Linux-lts-quantalUbuntuupstream*
Linux-lts-raringUbuntuprecise*
Linux-lts-raringUbuntuupstream*
Linux-lts-saucyUbuntuprecise*
Linux-lts-saucyUbuntuupstream*
Linux-lts-trustyUbuntuprecise*
Linux-lts-trustyUbuntuprecise/esm*
Linux-lts-trustyUbuntuupstream*
Linux-lts-utopicUbuntuupstream*
Linux-lts-vividUbuntuupstream*
Linux-lts-wilyUbuntuupstream*
Linux-lts-xenialUbuntuupstream*
Linux-maguroUbuntusaucy*
Linux-maguroUbuntutrusty*
Linux-maguroUbuntuupstream*
Linux-makoUbuntusaucy*
Linux-makoUbuntutrusty*
Linux-makoUbuntutrusty/esm*
Linux-makoUbuntuupstream*
Linux-makoUbuntuutopic*
Linux-makoUbuntuvivid*
Linux-makoUbuntuvivid/stable-phone-overlay*
Linux-makoUbuntuwily*
Linux-makoUbuntuxenial*
Linux-makoUbuntuyakkety*
Linux-mantaUbuntusaucy*
Linux-mantaUbuntutrusty*
Linux-mantaUbuntutrusty/esm*
Linux-mantaUbuntuupstream*
Linux-mantaUbuntuutopic*
Linux-mantaUbuntuvivid*
Linux-mantaUbuntuwily*
Linux-mvl-doveUbuntulucid*
Linux-mvl-doveUbuntuupstream*
Linux-qcm-msmUbuntulucid*
Linux-qcm-msmUbuntuprecise*
Linux-qcm-msmUbuntuquantal*
Linux-qcm-msmUbuntuupstream*
Linux-raspi2Ubuntuupstream*
Linux-raspi2Ubuntuvivid/ubuntu-core*
Linux-snapdragonUbuntuupstream*
Linux-ti-omap4Ubuntuprecise*
Linux-ti-omap4Ubuntuquantal*
Linux-ti-omap4Ubuntusaucy*
Linux-ti-omap4Ubuntuupstream*

Potential Mitigations

  • Mitigation of resource exhaustion attacks requires that the target system either:

  • The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.

  • The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.

References

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2026 Aqua Security Software Ltd.   Privacy Policy | Terms of Use