Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/bind: security bump version to 9.20.26
Date: Fri, 31 Jul 2026 14:22:03 +0200	[thread overview]
Message-ID: <20260731122203.155707-1-thomas.perale@mind.be> (raw)
In-Reply-To: <20260723195710.1465177-1-bernd@kuhls.net>

In reply of:
> https://downloads.isc.org/isc/bind9/9.20.26/doc/arm/html/notes.html#notes-for-bind-9-20-26
> https://downloads.isc.org/isc/bind9/9.20.26/doc/arm/html/changelog.html
> https://seclists.org/oss-sec/2026/q3/208
> 
> Fixes
> 
> CVE-2026-10723: Incorrect acceptance of NSEC3 records
> CVE-2026-10822: Key Record using PRIVATEDNS algorithm may lead to unexpected exit
> CVE-2026-11331: Potential wildcard CNAME RPZ policy bypass
> CVE-2026-11605: Unnecessary validation of DNSSEC signed records
> CVE-2026-11622: Potential memory usage beyond configured limits
> CVE-2026-11721: Cache poisoning possible with label count discrepancy, RRSIG, and wildcards
> CVE-2026-12617: Record ordering based unexpected exit with CNAME or DNAME
> CVE-2026-13204: Unexpected exit in certain situations with NSEC and NSEC3 both present
> CVE-2026-13321: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>

Applied to 2025.02.x & 2026.05.x. Thanks

> ---
> Gitlab pipelines
> https://gitlab.com/bkuhls/buildroot/-/commits/78563f67d06099122f817ed8e1ea9c0794726c81
> show the same 13 broken defconfigs compared to the git tree without this
> bump:
> https://gitlab.com/bkuhls/buildroot/-/commits/2d23bf7cc9ebc2e86374021b5f07013fa2d85429
> No new build errors are introduced by this bump.
> 
>  package/bind/bind.hash | 4 ++--
>  package/bind/bind.mk   | 2 +-
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/package/bind/bind.hash b/package/bind/bind.hash
> index a1ff3c6101..eb39e4b057 100644
> --- a/package/bind/bind.hash
> +++ b/package/bind/bind.hash
> @@ -1,4 +1,4 @@
> -# Verified from https://ftp.isc.org/isc/bind9/9.20.24/bind-9.20.24.tar.xz.asc
> +# Verified from https://ftp.isc.org/isc/bind9/9.20.26/bind-9.20.26.tar.xz.asc
>  # with key D99CCEAF879747014F038D63182E23579462EFAA
> -sha256  989fef1fc88ea59d04cd86f854dca5a4616a20a9968bcdde3c1a3668ab36be08  bind-9.20.24.tar.xz
> +sha256  55248def0f870c4c46b3de72978ea972615131516663188a4564dca1d20bf350  bind-9.20.26.tar.xz
>  sha256  9734825d67a3ac967b2c2f7c9a83c9e5db1c2474dbe9599157c3a4188749ebd4  COPYRIGHT
> diff --git a/package/bind/bind.mk b/package/bind/bind.mk
> index 2b8156d0d0..172bbf79b5 100644
> --- a/package/bind/bind.mk
> +++ b/package/bind/bind.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -BIND_VERSION = 9.20.24
> +BIND_VERSION = 9.20.26
>  BIND_SOURCE= bind-$(BIND_VERSION).tar.xz
>  BIND_SITE = https://ftp.isc.org/isc/bind9/$(BIND_VERSION)
>  BIND_INSTALL_STAGING = YES
> -- 
> 2.47.3
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2026-07-31 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23 19:57 [Buildroot] [PATCH 1/1] package/bind: security bump version to 9.20.26 Bernd Kuhls
2026-07-23 21:10 ` Julien Olivain via buildroot
2026-07-31 12:22 ` Thomas Perale via buildroot [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260731122203.155707-1-thomas.perale@mind.be \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=thomas.perale@mind.be \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox