Описание
Security update for bind
This update for bind fixes the following issues:
- CVE-2026-19033: Unauthenticated IXFR deltas are applied to the live zone before TSIG verification (bsc#1280430).
- CVE-2026-19662: qpcache NOQNAME proof use-after-free crashes recursive resolver (bsc#1280432).
- CVE-2026-19666: Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path (bsc#1280433).
- CVE-2026-19667: Remote assertion failure via 16-bit length truncation in dns_ncache_add() (bsc#1280435).
- CVE-2026-19668: Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching (bsc#1280436).
- CVE-2026-19941: checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof (bsc#1280437).
- CVE-2026-75029: Message parser retains every identical singleton RDATA, enabling wire-to-work amplification (bsc#1280438).
- CVE-2026-76163: named aborts on a TKEY query when the user configuration has no global options statement (bsc#1280439).
- CVE-2026-77119: NSEC3 insecure-referral proof can use unrelated cached NSEC3 RRsets (bsc#1280440).
- CVE-2026-77692: Unauthenticated remote crash of named via a single DoH SIG(0) request (bsc#1280441).
- CVE-2026-78301: Out-of-zone database nodes can become authoritative zone cuts (bsc#1280442).
- CVE-2026-80274: Validating resolver can abort while caching a mismatched NOQNAME proof (bsc#1280443).
- CVE-2026-81563: SVCB AliasMode additional-data error leaks qpcache references (bsc#1280444).
- CVE-2026-81736: Remote CPU denial of service through cached SVCB/HTTPS AliasMode trees (bsc#1280445).
Changes for bind:
Upgrade to release 9.20.29
New Features:
- Disclose active Negative Trust Anchors with Extended DNS Error
Feature Changes:
- Reject oversized and malformed DNSKEY records up front.
- Speed up RPZ policy zone updates. Bug Fixes:
- Prevent a crash when using both dns64 and filter-a.
- Stop passing UDP client addresses to update-policy external helpers.
- Missing required NSEC3 for delegation not detected.
- Tighten EUI48 and EUI64 text parsing.
- GeoIP ACL state could be stale or wrong after reload.
- Honor DNSSEC policy key tag ranges.
- Fix a double free in mdig when EDNS options are specified.
- Fix a crash when an IXFR falls back to AXFR with updates still pending.
- Fix DS requests to parental agents over TLS.
- Fix the rndc-confgen -q (quiet) option.
- Enforce query ACLs for redirect zones and searched DLZs.
- Check asnum validity in GeoIP ACLs.
- Fix a crash on remote-servers lists that reference themselves.
- A record from outside a response policy zone could crash named.
- Invalid key-store configuration could abort the DNSSEC tools.
- NSEC signature set could bypass the secure-delegation check.
- Fix a possible nsupdate issue when using GSS-TSIG.
- Fix a crash with a single-element geoip sortlist.
- Prevent out-of-bailiwick CNAMEs from evicting cached records.
- Restore periodic cleanup of stale resolver address data.
- Fix named-checkconf/named crash with malformed key name.
- Prevent resolver crashes while processing DNS over TCP.
- Ensure NSEC authority does not cross zonecut boundary.
- Treat an unusable NSEC3 chain as a verification failure.
- Treat non-canonical RPZ prefixes as any other failure.
- Negative caching stopped working with stale-answer-client-timeout set to 0.
- An unterminated OpenSSL private-key Label: field could be read past its parser buffer.
- Restore SMF support on Solaris and illumos.
- Fix compilation on GNU/Hurd.
- dig +yaml was producing invalid YAML when a lookup failed.
- Properly prevent TSIG generation command line injection attacks.
- Fix a potential heap bounds overflow write in dnssec-signzone.
- Fix crashes on invalid DNSTAP input in dnstap-read.
Список пакетов
SUSE Linux Enterprise Module for Basesystem 15 SP7
SUSE Linux Enterprise Module for Server Applications 15 SP7
Ссылки
- Link for SUSE-SU-2026:4285-1
- E-Mail link for SUSE-SU-2026:4285-1
- SUSE Security Ratings
- SUSE Bug 1280430
- SUSE Bug 1280432
- SUSE Bug 1280433
- SUSE Bug 1280435
- SUSE Bug 1280436
- SUSE Bug 1280437
- SUSE Bug 1280438
- SUSE Bug 1280439
- SUSE Bug 1280440
- SUSE Bug 1280441
- SUSE Bug 1280442
- SUSE Bug 1280443
- SUSE Bug 1280444
- SUSE Bug 1280445
- SUSE CVE CVE-2026-19033 page
- SUSE CVE CVE-2026-19662 page
- SUSE CVE CVE-2026-19666 page
Описание
For a secondary zone with transfers restricted by TSIG, `named` may start to serve the data provided in a zone transfer before the final message with the TSIG signature arrives. This could allow an attacker that does not actually possess a valid TSIG signature to send unauthorized zone contents to a secondary server. Although no TSIG signature ever arrives, `named` does not rollback to the pre-transfer state. To exploit the vulnerability, the transfer must be a multi-message TCP IXFR, as described by RFC 8945. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
Затронутые продукты
Ссылки
- CVE-2026-19033
- SUSE Bug 1280430
Описание
An attacker may be able to cause a `named` resolver to abort. The attack requires inducing the victim resolver to send multiple queries for a DNSSEC-signed zone hosted by an authoritative server under the control of the attacker. If the auth responds with a particular sequence of crafted answers, and those answers arrive in a particular order with particular timing, the `named` resolver will encounter a use-after-free bug, and abort. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
Затронутые продукты
Ссылки
- CVE-2026-19662
- SUSE Bug 1280432
Описание
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.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
Затронутые продукты
Ссылки
- CVE-2026-19666
- SUSE Bug 1280433
Описание
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 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
Затронутые продукты
Ссылки
- CVE-2026-19667
- SUSE Bug 1280435
Описание
A BIND recursive resolver may experience excessive resource consumption if it encounters large numbers of a particular kind of invalid DNSSEC record. Default limits on "max-records-per-type" and "max-types-per-name" help mitigate the exposure. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
Затронутые продукты
Ссылки
- CVE-2026-19668
- SUSE Bug 1280436
Описание
An inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an upstream level of the zone name to mask the existence of a victim's wildcard record. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
Затронутые продукты
Ссылки
- CVE-2026-19941
- SUSE Bug 1280437
Описание
In a query response, an attacker may send `named` multiple copies of a record that should only exist once (such as an SOA record). If the RDATA is the same on all the copies, the record is appended to the in-memory RDATA set, which can cause increased memory usage of the negative cache and possibly lead to other memory attack vectors. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
Затронутые продукты
Ссылки
- CVE-2026-75029
- SUSE Bug 1280438
Описание
If BIND is loaded with a "`named.conf`" file that contains no global "`options`" block, an attacker can send a query of QTYPE TKEY which may cause an assertion failure and subsequent unexpected program exit. This issue affects BIND 9 versions 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, and 9.20.9-S1 through 9.20.27-S1.
Затронутые продукты
Ссылки
- CVE-2026-76163
- SUSE Bug 1280439
Описание
A validly signed NSEC3 from an unrelated sibling zone may be accepted as an insecurity proof, downgrading a secure delegation and letting a forged unsigned answer through. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
Затронутые продукты
Ссылки
- CVE-2026-77119
- SUSE Bug 1280440
Описание
An attacker can cause `named` to abort by sending a crafted DNS-over-HTTPS request with a cryptographically invalid SIG(0) record, and then closing the transport connection prematurely. This issue affects BIND 9 versions 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, and 9.20.9-S1 through 9.20.27-S1.
Затронутые продукты
Ссылки
- CVE-2026-77692
- SUSE Bug 1280441
Описание
A malformed zone may contain an NS or DNAME node above its origin, which `named` treats as a zone cut. If an attacker inserts a malformed zone into a BIND authoritative server (e.g., via zone transfer), queries for names inside the configured zone then lose authoritative status and return an out-of-zone delegation. On a server that also provides recursion BIND can follow this locally sourced cut and cache attacker-supplied data, affecting names outside the configured zone. This situation persists as long as the malformed zone remains in the zone database. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
Затронутые продукты
Ссылки
- CVE-2026-78301
- SUSE Bug 1280442
Описание
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. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
Затронутые продукты
Ссылки
- CVE-2026-80274
- SUSE Bug 1280443
Описание
A BIND resolver encountering an SVCB/HTTPS AliasMode record referencing 14 or more SVCB/HTTPS ServiceMode records may fail to properly deallocate internal resources. If this happens repeatedly, resource exhaustion will eventually prevent the resolver from performing new recursive lookups. This issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.18.11-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
Затронутые продукты
Ссылки
- CVE-2026-81563
- SUSE Bug 1280444
Описание
If a BIND resolver has cached a tree of SVCB/HTTPS AliasMode records, and is then queried for the root of that tree, the resolver will spend disproportionate CPU time constructing the response. This issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.18.11-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
Затронутые продукты
Ссылки
- CVE-2026-81736
- SUSE Bug 1280445