Vulnerabilities
Misconfiguration
Compliance
CVE Vulnerabilities

CVE-2014-3611

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Published: Nov 10, 2014 | Modified: Apr 12, 2025
CVSS 3.x
4.7
MEDIUM
Source:
NVD
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
4.7 MEDIUM
AV:L/AC:M/Au:N/C:N/I:N/A:C
RedHat/V2
5.5 IMPORTANT
AV:A/AC:L/Au:S/C:N/I:N/A:C
RedHat/V3
Ubuntu
HIGH
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-3611
CWEhttps://cwe.mitre.org/data/definitions/362.html

Race condition in the __kvm_migrate_pit_timer function in arch/x86/kvm/i8254.c in the KVM subsystem in the Linux kernel through 3.17.2 allows guest OS users to cause a denial of service (host OS crash) by leveraging incorrect PIT emulation.

Weakness

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Affected Software

NameVendorStart VersionEnd Version
Linux_kernelLinux*3.17.2 (including)
Red Hat Enterprise Linux 5RedHatkvm-0:83-270.el5_11*
Red Hat Enterprise Linux 6RedHatkernel-0:2.6.32-504.1.3.el6*
Red Hat Enterprise Linux 6.5 Extended Update SupportRedHatkernel-0:2.6.32-431.50.1.el6*
Red Hat Enterprise Linux 7RedHatkernel-0:3.10.0-123.9.2.el7*
RHEV 3.X Hypervisor and Agents for RHEL-6RedHatrhev-hypervisor6-0:6.6-20150123.1.el6ev*
LinuxUbuntuesm-infra-legacy/trusty*
LinuxUbuntulucid*
LinuxUbuntuprecise*
LinuxUbuntuprecise/esm*
LinuxUbuntutrusty*
LinuxUbuntutrusty/esm*
LinuxUbuntuupstream*
LinuxUbuntuutopic*
Linux-armadaxpUbuntuprecise*
Linux-armadaxpUbuntuupstream*
Linux-awsUbuntuupstream*
Linux-ec2Ubuntulucid*
Linux-ec2Ubuntuupstream*
Linux-floUbuntutrusty*
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-goldfishUbuntutrusty*
Linux-goldfishUbuntuupstream*
Linux-goldfishUbuntuutopic*
Linux-goldfishUbuntuvivid*
Linux-goldfishUbuntuwily*
Linux-goldfishUbuntuxenial*
Linux-goldfishUbuntuyakkety*
Linux-goldfishUbuntuzesty*
Linux-grouperUbuntutrusty*
Linux-grouperUbuntuupstream*
Linux-grouperUbuntuutopic*
Linux-hweUbuntuupstream*
Linux-hwe-edgeUbuntuupstream*
Linux-linaro-omapUbuntuprecise*
Linux-linaro-omapUbuntuupstream*
Linux-linaro-sharedUbuntuprecise*
Linux-linaro-sharedUbuntuupstream*
Linux-linaro-vexpressUbuntuprecise*
Linux-linaro-vexpressUbuntuupstream*
Linux-lts-quantalUbuntuprecise*
Linux-lts-quantalUbuntuupstream*
Linux-lts-raringUbuntuprecise*
Linux-lts-raringUbuntuprecise/esm*
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-maguroUbuntutrusty*
Linux-maguroUbuntuupstream*
Linux-makoUbuntutrusty*
Linux-makoUbuntuupstream*
Linux-makoUbuntuutopic*
Linux-makoUbuntuvivid*
Linux-makoUbuntuvivid/stable-phone-overlay*
Linux-makoUbuntuwily*
Linux-makoUbuntuxenial*
Linux-makoUbuntuyakkety*
Linux-mantaUbuntutrusty*
Linux-mantaUbuntuupstream*
Linux-mantaUbuntuutopic*
Linux-mantaUbuntuvivid*
Linux-mantaUbuntuwily*
Linux-mvl-doveUbuntulucid*
Linux-mvl-doveUbuntuupstream*
Linux-qcm-msmUbuntulucid*
Linux-qcm-msmUbuntuprecise*
Linux-qcm-msmUbuntuupstream*
Linux-raspi2Ubuntuupstream*
Linux-raspi2Ubuntuvivid/ubuntu-core*
Linux-snapdragonUbuntuupstream*
Linux-ti-omap4Ubuntuprecise*
Linux-ti-omap4Ubuntuupstream*

Extended Description

A race condition occurs within concurrent environments, and it is effectively a property of a code sequence. Depending on the context, a code sequence may be in the form of a function call, a small number of instructions, a series of program invocations, etc. A race condition violates these properties, which are closely related:

A race condition exists when an “interfering code sequence” can still access the shared resource, violating exclusivity. The interfering code sequence could be “trusted” or “untrusted.” A trusted interfering code sequence occurs within the product; it cannot be modified by the attacker, and it can only be invoked indirectly. An untrusted interfering code sequence can be authored directly by the attacker, and typically it is external to the vulnerable product.

Potential Mitigations

  • Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.
  • Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).

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