Summary
[32:9.16.23-0.22-16]
- Backport 'Do not use header_prev in expire_lru_headers' from upstream.
[32:9.16.23-0.22-15]
- Reenable unit tests during build
[32:9.16.23-0.22.14]
- Prevent assertion failure in dns64 mode with break-dnssec yes (CVE-2026-19666)
- Prevent crash on wildcard responses containing both NSEC and NSEC3 proofs (CVE-2026-80274)
- Reject oversized negative cached records early (CVE-2026-19667)
Fixed packages 9
| Release | Package | Fixed in |
|---|---|---|
| Oracle Linux · 8 | bind9.16 | 32:9.16.23-0.22.el8_10.16 |
| Oracle Linux · 8 | bind9.16-chroot | 32:9.16.23-0.22.el8_10.16 |
| Oracle Linux · 8 | bind9.16-devel | 32:9.16.23-0.22.el8_10.16 |
| Oracle Linux · 8 | bind9.16-dnssec-utils | 32:9.16.23-0.22.el8_10.16 |
| Oracle Linux · 8 | bind9.16-doc | 32:9.16.23-0.22.el8_10.16 |
| Oracle Linux · 8 | bind9.16-libs | 32:9.16.23-0.22.el8_10.16 |
| Oracle Linux · 8 | bind9.16-license | 32:9.16.23-0.22.el8_10.16 |
| Oracle Linux · 8 | bind9.16-utils | 32:9.16.23-0.22.el8_10.16 |
| Oracle Linux · 8 | python3-bind9.16 | 32:9.16.23-0.22.el8_10.16 |
Vulnerabilities 3
-
High 7.5
Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path
On a resolver configured to use ``dns64``, if an applicable answer from the authoritative server is malformed in a specific way, the resolver `named` process will exit unexpectedly. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.2…
-
High 7.5
Remote assertion failure via 16-bit length truncation in `dns_ncache_add()`
If an attacker-controlled authoritative server can produce a negative answer that is exactly 65536 bytes, then a flaw in `named` results in a negative cache entry of 0 bytes. When this entry is subsequently read, `named` aborts. This issue affects BIND 9 vers…
-
High 7.5
Validating resolver can abort while caching a mismatched NOQNAME proof
If a BIND resolver sends a query for a DNSSEC-signed authoritative zone, and the authoritative server replies with a valid wildcard answer and signed NSEC3 proof, followed by an unsigned NSEC at the same owner name, it will trigger an unexpected program exit.…