CVE Vulnerabilities

CVE-2011-0695

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

Published: Mar 15, 2011 | Modified: Apr 11, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
5.7 MEDIUM
AV:A/AC:M/Au:N/C:N/I:N/A:C
RedHat/V2
6.1 IMPORTANT
AV:A/AC:L/Au:N/C:N/I:N/A:C
RedHat/V3
Ubuntu
MEDIUM

Race condition in the cm_work_handler function in the InfiniBand driver (drivers/infiniband/core/cma.c) in Linux kernel 2.6.x allows remote attackers to cause a denial of service (panic) by sending an InfiniBand request while other request handlers are still running, which triggers an invalid pointer dereference.

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

Name Vendor Start Version End Version
Linux_kernel Linux 2.6.0 (including) 2.6.39.4 (including)
MRG for RHEL-5 RedHat kernel-rt-0:2.6.33.9-rt31.64.el5rt *
Red Hat Enterprise Linux 5 RedHat kernel-0:2.6.18-238.19.1.el5 *
Red Hat Enterprise Linux 6 RedHat kernel-0:2.6.32-71.24.1.el6 *
Linux Ubuntu hardy *
Linux Ubuntu karmic *
Linux Ubuntu lucid *
Linux Ubuntu maverick *
Linux Ubuntu natty *
Linux Ubuntu upstream *
Linux-ec2 Ubuntu karmic *
Linux-ec2 Ubuntu lucid *
Linux-ec2 Ubuntu maverick *
Linux-ec2 Ubuntu upstream *
Linux-fsl-imx51 Ubuntu karmic *
Linux-fsl-imx51 Ubuntu lucid *
Linux-fsl-imx51 Ubuntu upstream *
Linux-lts-backport-maverick Ubuntu lucid *
Linux-lts-backport-maverick Ubuntu upstream *
Linux-lts-backport-natty Ubuntu upstream *
Linux-mvl-dove Ubuntu karmic *
Linux-mvl-dove Ubuntu lucid *
Linux-mvl-dove Ubuntu maverick *
Linux-mvl-dove Ubuntu upstream *
Linux-source-2.6.15 Ubuntu dapper *
Linux-source-2.6.15 Ubuntu upstream *
Linux-ti-omap4 Ubuntu maverick *
Linux-ti-omap4 Ubuntu natty *
Linux-ti-omap4 Ubuntu upstream *

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