Race condition in the kernel in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2, R2, and R2 SP1, Windows 7 Gold and SP1, Windows 8, Windows Server 2012, and Windows RT allows local users to gain privileges via a crafted application that leverages improper handling of objects in memory, aka Kernel Race Condition Vulnerability.
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.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Windows_7 | Microsoft | * | * |
| Windows_8 | Microsoft | - (including) | - (including) |
| Windows_rt | Microsoft | - (including) | - (including) |
| Windows_server_2003 | Microsoft | * | * |
| Windows_server_2008 | Microsoft | * | * |
| Windows_server_2012 | Microsoft | - (including) | - (including) |
| Windows_vista | Microsoft | * | * |
| Windows_xp | Microsoft | * | * |
| Windows_xp | Microsoft | –sp2 (including) | –sp2 (including) |
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.