crossbeam-utils provides atomics, synchronization primitives, scoped threads, and other utilities for concurrent programming in Rust. crossbeam-utils prior to version 0.8.7 incorrectly assumed that the alignment of {i,u}64
was always the same as Atomic{I,U}64
. However, the alignment of {i,u}64
on a 32-bit target can be smaller than Atomic{I,U}64
. This can cause unaligned memory accesses and data race. Crates using fetch_*
methods with AtomicCell<{i,u}64>
are affected by this issue. 32-bit targets without Atomic{I,U}64
and 64-bit targets are not affected by this issue. This has been fixed in crossbeam-utils 0.8.7. There are currently no known workarounds.
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 |
---|---|---|---|
Crossbeam | Crossbeam_project | * | 0.8.7 (excluding) |
Cargo | Ubuntu | bionic | * |
Cargo | Ubuntu | esm-apps/xenial | * |
Cargo | Ubuntu | impish | * |
Cargo | Ubuntu | kinetic | * |
Cargo | Ubuntu | trusty | * |
Cargo | Ubuntu | xenial | * |
Firefox | Ubuntu | bionic | * |
Firefox | Ubuntu | devel | * |
Firefox | Ubuntu | focal | * |
Firefox | Ubuntu | impish | * |
Firefox | Ubuntu | jammy | * |
Firefox | Ubuntu | kinetic | * |
Firefox | Ubuntu | lunar | * |
Firefox | Ubuntu | mantic | * |
Firefox | Ubuntu | noble | * |
Firefox | Ubuntu | oracular | * |
Firefox | Ubuntu | plucky | * |
Firefox | Ubuntu | trusty | * |
Firefox | Ubuntu | xenial | * |
Librsvg | Ubuntu | trusty | * |
Librsvg | Ubuntu | xenial | * |
Mozjs38 | Ubuntu | bionic | * |
Mozjs38 | Ubuntu | esm-apps/bionic | * |
Mozjs38 | Ubuntu | upstream | * |
Mozjs52 | Ubuntu | bionic | * |
Mozjs52 | Ubuntu | esm-apps/focal | * |
Mozjs52 | Ubuntu | esm-infra/bionic | * |
Mozjs52 | Ubuntu | focal | * |
Mozjs52 | Ubuntu | upstream | * |
Mozjs68 | Ubuntu | esm-infra/focal | * |
Mozjs68 | Ubuntu | focal | * |
Mozjs68 | Ubuntu | upstream | * |
Mozjs78 | Ubuntu | esm-apps/jammy | * |
Mozjs78 | Ubuntu | impish | * |
Mozjs78 | Ubuntu | jammy | * |
Mozjs78 | Ubuntu | kinetic | * |
Mozjs78 | Ubuntu | lunar | * |
Mozjs78 | Ubuntu | upstream | * |
Rust-crossbeam-utils | Ubuntu | esm-apps/focal | * |
Rust-crossbeam-utils | Ubuntu | esm-apps/jammy | * |
Rust-crossbeam-utils | Ubuntu | focal | * |
Rust-crossbeam-utils | Ubuntu | impish | * |
Rust-crossbeam-utils | Ubuntu | jammy | * |
Rust-crossbeam-utils | Ubuntu | kinetic | * |
Rust-crossbeam-utils | Ubuntu | upstream | * |
Rust-crossbeam-utils-0.7 | Ubuntu | esm-apps/jammy | * |
Rust-crossbeam-utils-0.7 | Ubuntu | jammy | * |
Rust-crossbeam-utils-0.7 | Ubuntu | kinetic | * |
Rustc | Ubuntu | bionic | * |
Rustc | Ubuntu | esm-apps/focal | * |
Rustc | Ubuntu | esm-apps/xenial | * |
Rustc | Ubuntu | esm-infra-legacy/trusty | * |
Rustc | Ubuntu | focal | * |
Rustc | Ubuntu | impish | * |
Rustc | Ubuntu | jammy | * |
Rustc | Ubuntu | kinetic | * |
Rustc | Ubuntu | trusty | * |
Rustc | Ubuntu | trusty/esm | * |
Rustc | Ubuntu | xenial | * |
Thunderbird | Ubuntu | bionic | * |
Thunderbird | Ubuntu | devel | * |
Thunderbird | Ubuntu | focal | * |
Thunderbird | Ubuntu | impish | * |
Thunderbird | Ubuntu | jammy | * |
Thunderbird | Ubuntu | kinetic | * |
Thunderbird | Ubuntu | lunar | * |
Thunderbird | Ubuntu | mantic | * |
Thunderbird | Ubuntu | noble | * |
Thunderbird | Ubuntu | oracular | * |
Thunderbird | Ubuntu | plucky | * |
Thunderbird | Ubuntu | trusty | * |
Thunderbird | Ubuntu | xenial | * |
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.