Undefined behavior may result due to a race condition leading to a use-after-free violation. If BIND receives an incoming DNS message signed with SIG(0), it begins work to validate that signature. If, during that validation, the recursive-clients limit is reached (as would occur during a query flood), and that same DNS message is discarded per the limit, there is a brief window of time while the SIG(0) validation may attempt to read the now-discarded DNS message. This issue affects BIND 9 versions 9.20.0 through 9.20.22, 9.21.0 through 9.21.21, and 9.20.9-S1 through 9.20.22-S1. BIND 9 versions 9.18.28 through 9.18.49 and 9.18.28-S1 through 9.18.49-S1 are NOT affected.
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 |
|---|---|---|---|
| Bind | Isc | 9.20.0 (including) | 9.20.23 (excluding) |
| Bind | Isc | 9.21.0 (including) | 9.21.22 (excluding) |
| Red Hat Hardened Images | RedHat | bind-main-9.18.48-1.1.hum1 | * |
| Bind9 | Ubuntu | devel | * |
| Bind9 | Ubuntu | questing | * |
| Bind9 | Ubuntu | resolute | * |
| Bind9 | 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).
Related Attack Patterns
References
- https://downloads.isc.org/isc/bind9/9.20.23
- https://downloads.isc.org/isc/bind9/9.21.22
- https://kb.isc.org/docs/cve-2026-5947
- https://access.redhat.com/errata/RHSA-2026:7412
- https://access.redhat.com/security/cve/CVE-2026-5947
- https://bugzilla.redhat.com/show_bug.cgi?id=2479772
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-5947.json