an anomalous behavior due to unexpected critical dependence on the relative timing of events
an undesirable situation that occurs when a device or system attempts to perform two or more operations at the same time, but because of the nature of the device or system, the operations must be done in the proper sequence in order to be done correctly
a possible source for a defect, since the value of the variable at the time of reading depends on the scheduling
a situation in a multiple-threaded environment in which the result of the execution depends on the order of execution among the threads
a situation in which the outcome is dependent upon internal timing considerations
a situation in which two or more threads or processes are reading or writing some shared data, and the final result depends on the timing of how the threads are scheduled
a situation in which two threads access a variable simultaneously and the accesses are not both read accesses
a situation where a program performs an operation in several steps, and an attacker has the chance to catch it between steps and alter the system state
a situation where the result depends upon the relative speeds of the tasks or the outside world
a situation where two threads manipulate a data structure simultaneously, without synchronization
The act of each thread racing to complete its critical code section before some other thread enters that critical code section.
The condition which occurs when several processes or CPUs are trying to write to the same memory or disk locations at the same time. The data that is eventually stored depends on the order that the writes occur. A synchronization mechanism must be used to enforce the desired order in which the writes are to take place.
A situation in which the result of operations being executed by two or more processes depends on the order in which those processes execute, for example, if two processes and are to write different values and to the same variable.
The situation that can occur when a system attempts to perform two or more operations at the same time, or in an unexpected order.
A condition caused by the timing of events within or among software components. Race conditions typically are associated with synchronization errors that provide a window of opportunity during which one process can interfere with another, possibly introducing a security vulnerability.
A cause of concurrency problems. Multiple accesses to a shared resource, at least one of which is a write, with no mechanism used by either to moderate simultaneous access.
Situation in which multiple processes vie for the same resource and receive it in an unpredictable manner. Race conditions can lead to cases where applications do not run correctly from one invocation to the next.
Occurs when two or more threads perform an operation, and the result of the operation depends on unpredictable timing factors.
A race condition or race hazard is a flaw in a system or process whereby the output of the process is unexpectedly and critically dependent on the sequence or timing of other events. The term originates with the idea of two signals racing each other to influence the output first.