Skip to content
fr Sign in
7.5 High

CVE-2022-3924 This issue can affect BIND 9 resolvers with `stale-answer-enable yes;` that also make use of the option…

Description

This issue can affect BIND 9 resolvers with `stale-answer-enable yes;` that also make use of the option `stale-answer-client-timeout`, configured with a value greater than zero. If the resolver receives many queries that require recursion, there will be a corresponding increase in the number of clients that are waiting for recursion to complete. If there are sufficient clients already waiting when a new client query is received so that it is necessary to SERVFAIL the longest waiting client (see BIND 9 ARM `recursive-clients` limit and soft quota), then it is possible for a race to occur between providing a stale answer to this older client and sending an early timeout SERVFAIL, which may cause an assertion failure. This issue affects BIND 9 versions 9.16.12 through 9.16.36, 9.18.0 through 9.18.10, 9.19.0 through 9.19.8, and 9.16.12-S1 through 9.16.36-S1.

Affected products and versions

Product Affected versions Fixed in
BIND 9 9.19 9.19.0 → 9.19.8 No fix stated
BIND 9 9.18 9.18.0 → 9.18.10 No fix stated
BIND 9 9.16 9.16.12-S1 → 9.16.36 No fix stated

References

Timeline

  1. Published
  2. Last modified

Other CVEs of BIND 9

The 87 CVEs of BIND 9 →
CVE-2026-97313 A recursive BIND server that receives a query with recursion desired (RD=1) followed by a non-recursive query (RD=0) may… 7.5 High CVE-2026-96888 A BIND resolver that is configured with both a "redirect" zone and "qname-minimization strict" may abort with an… 7.5 High CVE-2026-94300 Replaying GSS-TSIG signed UDP messages can result in memory corruption in "`named`" 8.1 High CVE-2026-19630 In a BIND resolver, inbound DNS protocol messages with a particular structure will result in additional processing, with… 7.5 High
Track this CVE