In FreeBSD 12.1-STABLE before r359565, 12.1-RELEASE before p7, 11.4-STABLE before r362975, 11.4-RELEASE before p1, and 11.3-RELEASE before p11, missing synchronization in the IPV6_2292PKTOPTIONS socket option set handler contained a race condition allowing a malicious application to modify memory after being freed, possibly resulting in code execution.
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 |
|---|---|---|---|
| Freebsd | Freebsd | 11.3 (including) | 11.3 (including) |
| Freebsd | Freebsd | 11.3-p1 (including) | 11.3-p1 (including) |
| Freebsd | Freebsd | 11.3-p10 (including) | 11.3-p10 (including) |
| Freebsd | Freebsd | 11.3-p2 (including) | 11.3-p2 (including) |
| Freebsd | Freebsd | 11.3-p3 (including) | 11.3-p3 (including) |
| Freebsd | Freebsd | 11.3-p4 (including) | 11.3-p4 (including) |
| Freebsd | Freebsd | 11.3-p5 (including) | 11.3-p5 (including) |
| Freebsd | Freebsd | 11.3-p6 (including) | 11.3-p6 (including) |
| Freebsd | Freebsd | 11.3-p7 (including) | 11.3-p7 (including) |
| Freebsd | Freebsd | 11.3-p8 (including) | 11.3-p8 (including) |
| Freebsd | Freebsd | 11.3-p9 (including) | 11.3-p9 (including) |
| Freebsd | Freebsd | 11.4 (including) | 11.4 (including) |
| Freebsd | Freebsd | 11.4-beta1 (including) | 11.4-beta1 (including) |
| Freebsd | Freebsd | 11.4-rc2 (including) | 11.4-rc2 (including) |
| Freebsd | Freebsd | 12.1 (including) | 12.1 (including) |
| Freebsd | Freebsd | 12.1-p1 (including) | 12.1-p1 (including) |
| Freebsd | Freebsd | 12.1-p2 (including) | 12.1-p2 (including) |
| Freebsd | Freebsd | 12.1-p3 (including) | 12.1-p3 (including) |
| Freebsd | Freebsd | 12.1-p4 (including) | 12.1-p4 (including) |
| Freebsd | Freebsd | 12.1-p5 (including) | 12.1-p5 (including) |
| Freebsd | Freebsd | 12.1-p6 (including) | 12.1-p6 (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.