From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org,
Giulio Benetti <giulio.benetti@benettiengineering.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/bind: security bump version to 9.20.26
Date: Thu, 23 Jul 2026 23:10:24 +0200 [thread overview]
Message-ID: <ee154927759e1d14e507e7f4a52c6416@free.fr> (raw)
In-Reply-To: <20260723195710.1465177-1-bernd@kuhls.net>
On 23/07/2026 21:57, Bernd Kuhls wrote:
> 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 master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-07-23 21:10 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 [this message]
2026-07-31 12:22 ` Thomas Perale via buildroot
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=ee154927759e1d14e507e7f4a52c6416@free.fr \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=giulio.benetti@benettiengineering.com \
--cc=ju.o@free.fr \
/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