The `dig` and `host` commands core dump or give incomplete results in Ubuntu 22.04

[Fedon Kadifeli]

[Impact]

When using dig with the +nssearch option, the application will likely crash with a core dump. In this case the resulting list of domains will be incomplete.

The fix should be backported to Kinetic and Jammy to allow users to get all results of an nssearch on a domain.

The bug will be fixed by the minor release update described in (LP: #2003586) through upstream correcting IPv6 functionality.

[Test Plan]

# lxc launch images:ubuntu/{kinetic, jammy} test-bind9
# lxc exec test-bind9
# apt update && apt dist-upgrade -y
# apt install dnsutils -y
# dig +nssearch isc.org
- Before the update this leads to a crash ending in "Aborted (core dumped)" after failing to get a response from an ipv6 address while after it will show that there was a communication error with addresses it did not get a response from

[Where problems could occur]

Problems could occour in multiple areas outside of this fix because it is being added in a minor release update. Issues directly related to this fix would arise in the functionality of dig +nssearch, likely related to the handling of domains containing IPv6 addresses.

[Original Description]

The dig and host commands give incomplete results or (sometimes) give core dump on Ubuntu 22.04. Both commands are on version "9.18.1-1ubuntu1-Ubuntu."

When I run them like this:

$ dig google.com +nssearch

$ host -C google.com

most of the times the output is incomplete (no output or only a single line) and the other times they core dump. This happens on x86_64 systems. On aarch64 systems, they output some lines and then they hang.

All systems are Ubuntu 22.04 and command versions are the same as given above. Previous versions do not exhibit this problem.

Sample run:

$ dig google.com +nssearch
$ dig google.com +nssearch
$ dig google.com +nssearch
SOA ns1.google.com. dns-admin.google.com. 444034222 900 900 1800 60 from server 216.239.38.10 in 0 ms.
$ dig google.com +nssearch
SOA ns1.google.com. dns-admin.google.com. 444217784 900 900 1800 60 from server 216.239.32.10 in 8 ms.
$ dig google.com +nssearch
SOA ns1.google.com. dns-admin.google.com. 444034222 900 900 1800 60 from server 216.239.34.10 in 0 ms.
dighost.c:1517: INSIST((uint_fast32_t) __extension__ ({ __auto_type __atomic_load_ptr = ((&recvcount)); __typeof__ ((void)0, *__atomic_load_ptr) __atomic_load_tmp; __atomic_load (__atomic_load_ptr, &__atomic_load_tmp, (memory_order_acquire)); __atomic_load_tmp; }) == 0) failed, back trace
/lib/x86_64-linux-gnu/libisc-9.18.1-1ubuntu1-Ubuntu.so(+0x32083)[0x7f821fafc083]
/lib/x86_64-linux-gnu/libisc-9.18.1-1ubuntu1-Ubuntu.so(isc_assertion_failed+0x10)[0x7f821fafb570]
dig(+0x11de1)[0x55afb566fde1]
dig(+0xc7cd)[0x55afb566a7cd]
dig(+0xfdc2)[0x55afb566ddc2]
/lib/x86_64-linux-gnu/libisc-9.18.1-1ubuntu1-Ubuntu.so(isc__nm_async_readcb+0xb1)[0x7f821faeac41]
/lib/x86_64-linux-gnu/libisc-9.18.1-1ubuntu1-Ubuntu.so(isc__nm_readcb+0x9b)[0x7f821faead7b]
/lib/x86_64-linux-gnu/libisc-9.18.1-1ubuntu1-Ubuntu.so(+0x2b0d0)[0x7f821faf50d0]
/lib/x86_64-linux-gnu/libisc-9.18.1-1ubuntu1-Ubuntu.so(isc__nm_udp_read_cb+0x4a)[0x7f821faf526a]
/lib/x86_64-linux-gnu/libuv.so.1(+0x23e6b)[0x7f821f612e6b]
/lib/x86_64-linux-gnu/libuv.so.1(+0x2511e)[0x7f821f61411e]
/lib/x86_64-linux-gnu/libuv.so.1(uv_run+0x678)[0x7f821f5fdc88]
/lib/x86_64-linux-gnu/libisc-9.18.1-1ubuntu1-Ubuntu.so(+0x25eae)[0x7f821faefeae]
/lib/x86_64-linux-gnu/libisc-9.18.1-1ubuntu1-Ubuntu.so(isc__trampoline_run+0x1a)[0x7f821fb1f7ba]
/lib/x86_64-linux-gnu/libc.so.6(+0x94b43)[0x7f821f6b5b43]
/lib/x86_64-linux-gnu/libc.so.6(+0x126a00)[0x7f821f747a00]
Aborted (core dumped)

[Lucas Kanashiro (lucaskanashiro)]

Thanks for taking the time to file this bug and trying to make Ubuntu better.

I did try to run the same command you did in a clean Jammy lxd container and it just hangs:

root@bind9-test:~# dig google.com +nssearch
SOA ns1.google.com. dns-admin.google.com. 444516783 900 900 1800 60 from server 2001:4860:4802:34::a in 72 ms.
SOA ns1.google.com. dns-admin.google.com. 444516783 900 900 1800 60 from server 2001:4860:4802:32::a in 76 ms.
SOA ns1.google.com. dns-admin.google.com. 444516783 900 900 1800 60 from server 216.239.32.10 in 80 ms.
SOA ns1.google.com. dns-admin.google.com. 444516783 900 900 1800 60 from server 216.239.34.10 in 80 ms.
SOA ns1.google.com. dns-admin.google.com. 444217784 900 900 1800 60 from server 216.239.36.10 in 140 ms.
SOA ns1.google.com. dns-admin.google.com. 444217784 900 900 1800 60 from server 216.239.38.10 in 140 ms.
SOA ns1.google.com. dns-admin.google.com. 444217784 900 900 1800 60 from server 2001:4860:4802:36::a in 144 ms.
SOA ns1.google.com. dns-admin.google.com. 444217784 900 900 1800 60 from server 2001:4860:4802:38::a in 144 ms.

The command stays running forever. I was not able to get the core dump you got but seems that something undesired is happening.

[Sergio Durigan Junior (sergiodj)]

Thanks for the bug report, Fedon.

I have tried reproducing the crash using the steps provided by you (inside a Jammy amd64 container), but I got the same results as Lucas: "dig google.com +nssearch" would hang there indefinitely, but won't crash.

I was able to make it crash when I appended "+tcp" to the command:

# dig google.com +nssearch +tcp
dighost.c:1683: INSIST(query->readhandle == ((void *)0)) failed, back trace
/lib/x86_64-linux-gnu/libisc-9.18.1-1ubuntu1-Ubuntu.so(+0x32083)[0x7f193d786083]
/lib/x86_64-linux-gnu/libisc-9.18.1-1ubuntu1-Ubuntu.so(isc_assertion_failed+0x10)[0x7f193d785570]
...

but the assertion that's been triggered is different than the one you're seeing.

Unfortunately there are several problems with dig on bind9 9.18.1, so it's hard to determine if these two errors are the same. I'd like to ask for your help in testing a possible fix for this problem. If I prepare a PPA with a candidate fix, would you be able to give it a try and let me know the results?

Thanks in advance.

[Fedon Kadifeli (fedkad)]

I have a Google Cloud instance (x86_64), a local VirtualBox virtual desktop instance (x86_64), and an Oracle Cloud (aarch64) instance, as I mentioned above. I haven't upgraded my physical notebook yet.

I can test your PPA on any or all of these virtual machines. Just give me the instructions. Thanks.

Note: The hang may be related to IPv6 connectivity, since in my test servers only the Oracle Cloud (aarch64) instance has IPv6 (global) address. Just a thought though. :)

[Sergio Durigan Junior (sergiodj)]

On Wednesday, April 27 2022, Fedon Kadifeli wrote:

> I have a Google Cloud instance (x86_64), a local VirtualBox virtual
> desktop instance (x86_64), and an Oracle Cloud (aarch64) instance, as I
> mentioned above. I haven't upgraded my physical notebook yet.
>
> I can test your PPA on any or all of these virtual machines. Just give
> me the instructions. Thanks.

Thank you, Fedon.

You can find the PPA here:

https://launchpad.net/~sergiodj/+archive/ubuntu/bind9-lp1970252

You just have to add it to the system, run apt-get update and then
upgrade the packages.

> Note: The hang may be related to IPv6 connectivity, since in my test
> servers only the Oracle Cloud (aarch64) instance has IPv6 (global)
> address. Just a thought though. :)

Yes, unfortunately bind9 9.18.1 has several problems with dig/host and
upstream is still addressing everything. For example, the build you
will find in the PPA above contains patches to fix the problem you've
reported, but you can still make dig crash if you something like:

  $ dig google.com +nssearch +tcp

I'm following upstream's progress closely, but I'm afraid it will take a
little bit of time until we can solve everything.

Thanks,

--
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14

[Fedon Kadifeli (fedkad)]

I tested your PPA Sergio today in one of my virtual systems (x86_64 with no IPv6 connectivity). Previously the commands were giving incomplete results or were crashing.

Now, *they consistently output NOTHING*:

$ dig google.com +nssearch

$ host -C google.com

$ dig -d google.com +nssearch
setup_libs()
setup_system()
create_search_list()
ndots is 1.
timeout is 0.
retries is 3.
get_server_list()
make_server(127.0.0.53)
dig_query_setup
parse_args()
making new lookup
make_empty_lookup()
make_empty_lookup() = 0x564a58fce100->references = 1
digrc (open)
main parsing -d
main parsing google.com
clone_lookup()
make_empty_lookup()
make_empty_lookup() = 0x564a58fcf560->references = 1
clone_server_list()
looking up google.com
main parsing +nssearch
dig_startup()
lock_lookup dighost.c:4324
success
start_lookup()
setup_lookup(0x564a58fcf560)
resetting lookup counter.
cloning server list
clone_server_list()
make_server(127.0.0.53)
idn_textname: google.com
using root origin
recursive query
AD query
add_question()
starting to render the message
add_opt()
done rendering
create query 0x7f8030016870 linked to lookup 0x564a58fcf560
dighost.c:2106:lookup_attach(0x564a58fcf560) = 2
dighost.c:2610:new_query(0x7f8030016870) = 1
do_lookup()
start_udp(0x7f8030016870)
dighost.c:2982:query_attach(0x7f8030016870) = 2
working on lookup 0x564a58fcf560, query 0x7f8030016870
dighost.c:3027:query_attach(0x7f8030016870) = 3
unlock_lookup dighost.c:4326
dighost.c:2944:query_attach(0x7f8030016870) = 4
recving with lookup=0x564a58fcf560, query=0x7f8030016870, handle=(nil)
recvcount=1
have local timeout of 5000
dighost.c:2888:query_attach(0x7f8030016870) = 5
sending a request
sendcount=1
dighost.c:1700:query_detach(0x7f8030016870) = 4
dighost.c:2964:query_detach(0x7f8030016870) = 3
send_done(0x7f803003a180, success, 0x7f8030016870)
sendcount=0
lock_lookup dighost.c:2638
success
dighost.c:2642:lookup_attach(0x564a58fcf560) = 3
dighost.c:2680:query_detach(0x7f8030016870) = 2
dighost.c:2681:lookup_detach(0x564a58fcf560) = 2
check_if_done()
list empty
unlock_lookup dighost.c:2684
recv_done(0x7f803003a180, success, 0x7f8036c6c880, 0x7f8030016870)
lock_lookup dighost.c:3631
success
recvcount=0
dighost.c:3636:lookup_attach(0x564a58fcf560) = 3
before parse starts
after parse
in NSSEARCH code
following up google.com
found NS set
found NS ns2.google.com
requeue_lookup()
clone_lookup()
make_empty_lookup()
make_empty_lookup() = 0x7f803003d250->references = 1
before insertion, init@0x564a58fcf560 -> 0xffffffffffffffff, new@0x7f803003d250 -> 0xffffffffffffffff
after insertion, init -> 0x564a58fcf560, new = 0x7f803003d250, new -> (nil)
dighost.c:1887:_cancel_lookup()
canceling pending query 0x7f8030016870, belonging to 0x564a58fcf560
dighost.c:2707:query_detach(0x7f8030016870) = 1
check_if_done()
list full
pending lookup 0x7f803003d250
adding server ns2.google.com
make_server(216.239.34.10)
make_server(2001:4860:4802:34::a)
found NS set
found NS ns4.google.com
adding server ns4.google.com
make_server(216.239.38.10)
make_server(2001:4860:4802:38::a)
found NS set
found NS ns3.google.com
adding server ns3.google.com
make_server(216.239.36.10)
make_server(2001:4860:4802:36::a)
found NS set
found NS...

[Sergio Durigan Junior (sergiodj)]

Hi,

Sorry about the absence, but I haven't forgotten about this bug. I'm following upstream's issues and they have been fixing (albeit a bit slowly) the bugs that are affecting dig.

Because we're talking about multiple bugs and several patches here, my plan is to actually do an MRE (microrelease update) of bind9 in Jammy, which should be easier than performing a massive SRU.

I will keep an eye on the progress being made by upstream and will update this bug when there's any significant development.

On a side note, I would like to strongly encourage anyone who is experience these dig bugs to comment on upstream's issues and let them know that you are affected. This will certainly help them prioritize things.

Thanks.

[Fedon Kadifeli (fedkad)]

Now that I have more 22.04 installations, I can say with 99% confidence that:

* the machines having IPv6 connectivity display their output, but after that they hang (always).
* the machines that don't have IPv6 connectivity either display incomplete (or empty) output or crash at the end.

[Sergio Durigan Junior (sergiodj)]

Thank you, Fedon. I am keeping track of the current upstream bugs related to "dig", but please feel free to also comment there and let upstream know that this is affecting you.

[Fedon Kadifeli (fedkad)]

Still the same at version "9.18.4-2ubuntu2-Ubuntu". :(

[Rolf Leggewie (r0lf)]

@Sergio, where are we supposed to comment upstream? It does not seem they have a public issue tracker. What's the best place?

[Sergio Durigan Junior (sergiodj)]

Hi,

We're working on merging bind9 9.18.10 in Lunar and, as far as I have checked, this bug is fixed there. This means that upstream has fixed the problem in the meantime, so now we have to work on identifying the proper patches and backport them to Jammy/Kinetic.

I'm adding a server-todo tag here in order to raise the priority of this bug for the Server team. On top of that, and perhaps even more importantly, Lena has been working on obtaining an MRE for bind9 on Jammy, which would effectively solve this bug without the need to backport anything. But that's still WIP and I don't know when (or if) we'll succeed.

I'm a bit swamped this week and will be on PTO next week, but I'll try to squeeze this bug in my TODO list and get it moving until Friday.

Thanks.

[Lena Voytek (lvoytek)]

Assigning myself to the development release while doing the mre for lunar

[Lena Voytek (lvoytek)]

Lunar has been updated to 9.18.10, fixing the core dump and incomplete information issues. I'm working on the MRE for Jammy and Kinetic to get them to the same place to match this behavior.

[Fedon Kadifeli (fedkad)]

Thanks for the effort! Any potential release date of 9.18.10 on Kinetic or Jammy?

[Lena Voytek (lvoytek)]

The release for Kinetic and Jammy should happen relatively soon. It may take some time to review the many changes to make sure all is good to go though. Updates on this process will show up on LP: #2003586

[Steve Langasek (vorlon)]

Hello Fedon, or anyone else affected,

Accepted bind9 into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bind9/1:9.18.12-0ubuntu0.22.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Steve Langasek (vorlon)]

Hello Fedon, or anyone else affected,

Accepted bind9 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bind9/1:9.18.12-0ubuntu0.22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted bind9 (1:9.18.12-0ubuntu0.22.10.1) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

testssl.sh/3.0.7+dfsg-1 (arm64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/kinetic/update_excuses.html#bind9

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Simon Déziel (sdeziel)]

I verified the -proposed package on a arm64 VM running Jammy. Before the update, `dig +nssearch google.com` would hang but after updating to -proposed:

# apt-get install bind9-dnsutils
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  bind9-host bind9-libs
The following packages will be upgraded:
  bind9-dnsutils bind9-host bind9-libs
3 upgraded, 0 newly installed, 0 to remove and 27 not upgraded.
Need to get 1409 kB of archives.
After this operation, 151 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://ca-montreal-1-ad-1.clouds.ports.ubuntu.com/ubuntu-ports jammy-proposed/main arm64 bind9-host arm64 1:9.18.12-0ubuntu0.22.04.1 [51.9 kB]
Get:2 http://ca-montreal-1-ad-1.clouds.ports.ubuntu.com/ubuntu-ports jammy-proposed/main arm64 bind9-dnsutils arm64 1:9.18.12-0ubuntu0.22.04.1 [158 kB]
Get:3 http://ca-montreal-1-ad-1.clouds.ports.ubuntu.com/ubuntu-ports jammy-proposed/main arm64 bind9-libs arm64 1:9.18.12-0ubuntu0.22.04.1 [1199 kB]
Fetched 1409 kB in 1s (1687 kB/s)
(Reading database ... 34244 files and directories currently installed.)
Preparing to unpack .../bind9-host_1%3a9.18.12-0ubuntu0.22.04.1_arm64.deb ...
Unpacking bind9-host (1:9.18.12-0ubuntu0.22.04.1) over (1:9.18.1-1ubuntu1.3) ...
Preparing to unpack .../bind9-dnsutils_1%3a9.18.12-0ubuntu0.22.04.1_arm64.deb ...
Unpacking bind9-dnsutils (1:9.18.12-0ubuntu0.22.04.1) over (1:9.18.1-1ubuntu1.3) ...
Preparing to unpack .../bind9-libs_1%3a9.18.12-0ubuntu0.22.04.1_arm64.deb ...
Unpacking bind9-libs:arm64 (1:9.18.12-0ubuntu0.22.04.1) over (1:9.18.1-1ubuntu1.3) ...
Setting up bind9-libs:arm64 (1:9.18.12-0ubuntu0.22.04.1) ...
Setting up bind9-host (1:9.18.12-0ubuntu0.22.04.1) ...
Setting up bind9-dnsutils (1:9.18.12-0ubuntu0.22.04.1) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for libc-bin (2.35-0ubuntu3.1) ...

It now works fine:

$ dig +nssearch google.com
SOA ns1.google.com. dns-admin.google.com. 517756399 900 900 1800 60 from server 2001:4860:4802:32::a in 16 ms.
SOA ns1.google.com. dns-admin.google.com. 517756399 900 900 1800 60 from server 2001:4860:4802:38::a in 12 ms.
SOA ns1.google.com. dns-admin.google.com. 517756399 900 900 1800 60 from server 216.239.38.10 in 12 ms.
SOA ns1.google.com. dns-admin.google.com. 517756399 900 900 1800 60 from server 216.239.32.10 in 12 ms.
SOA ns1.google.com. dns-admin.google.com. 517756399 900 900 1800 60 from server 216.239.36.10 in 24 ms.
SOA ns1.google.com. dns-admin.google.com. 517756399 900 900 1800 60 from server 2001:4860:4802:34::a in 20 ms.
SOA ns1.google.com. dns-admin.google.com. 517756399 900 900 1800 60 from server 216.239.34.10 in 20 ms.
SOA ns1.google.com. dns-admin.google.com. 517756399 900 900 1800 60 from server 2001:4860:4802:36::a in 20 ms.

$ echo $?
0

[Lena Voytek (lvoytek)]

Verified for Kinetic:

# lxc launch images:ubuntu/{kinetic, jammy} test-bind9
# lxc exec test-bind9

# cat <<EOF >/etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list
# Enable Ubuntu proposed archive
deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed restricted main multiverse universe
EOF

# apt update && apt dist-upgrade -y
# apt install dnsutils -y
# dig +nssearch isc.org

SOA ns-int.isc.org. hostmaster.isc.org. 2023031585 7200 3600 24796800 3600 from server 149.20.1.73 in 31 ms.
SOA ns-int.isc.org. hostmaster.isc.org. 2023031585 7200 3600 24796800 3600 from server 199.254.63.254 in 131 ms.
SOA ns-int.isc.org. hostmaster.isc.org. 2023031585 7200 3600 24796800 3600 from server 199.6.1.52 in 167 ms.
SOA ns-int.isc.org. hostmaster.isc.org. 2023031585 7200 3600 24796800 3600 from server 51.75.79.143 in 191 ms.
;; communications error to 2001:41d0:701:1100::2c92#53: timed out
;; communications error to 2001:500:60:d::52#53: timed out
;; communications error to 2001:500:2c::254#53: timed out
;; communications error to 2001:4f8:1:f::73#53: timed out

Dig does not crash - good to go

[Launchpad Janitor (janitor)]

This bug was fixed in the package bind9 - 1:9.18.12-0ubuntu0.22.04.1

---------------
bind9 (1:9.18.12-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream releases 9.18.2 - 9.18.12 (LP: #2003586)
    - Updates:
      + update-quota option
      + named -V shows supported cryptographic algorithms
      + Catalog Zones schema version 2 support in named
      + DNS error support Stale Answer and Stale NXDOMAIN Answer
      + Remote TLS certificate verification support
      + reusereport option
    - Bug Fixes Include:
      + Fix crash when using dig with +nssearch and +tcp (LP: #1258003)
      + Fix incomplete results using dig with +nssearch (LP: #1970252)
      + Fix loading of preinstalled plugins (LP: #2006972)
      + CVE-2022-2795, CVE-2022-2881, CVE-2022-2906, CVE-2022-3080,
        CVE-2022-38178, CVE-2022-3094, CVE-2022-3736, CVE-2022-3924,
        CVE-2022-1183
      + Fix thread safety in dns_dispatch
      + Fix ADB quota management in resolver
      + Fix Prohibited DNS error on allow-recursion
      + Fix crash when restarting server with active statschannel connection
      + Fix use after free for catalog zone processing
      + Fix leak of dns_keyfileio_t objects
      + Fix nslookup failure to use port option when record type ANY is used
      + Fix crash on dnssec-policy zone with NSEC3 and inline-signing turned on
      + Fix inheritance when setting remote server port
      + Fix assertion error when accessing statistics channel
      + Fix rndc dumpdb -expired for stuck cache
      + Fix check for other name servers after receiving FORMERR
      + Fix deletion of CDS after zone sign
      + Fix dighost query context management
      + Fix dig hanging due to IPv4 mapped IPv6 address
      + See https://bind9.readthedocs.io/en/v9_18_12/notes.html#notes-for-bind-9-18-12
        for additional bug fixes and information
  * Improve dep-8 test suite (LP: #2003584):
    - d/t/zonetest: Add dep8 test for checking the domain zone creation process
    - d/t/control: Add new test outline
  * d/bind9-doc.docs: Stop installing removed file doc/misc/options.active
  * Remove patches for bugs LP #1964400 and LP #1964686 fixed upstream:
    - lp1964400-lp1964686-Fix-an-issue-in-dig-when-retrying-with-the-next-serv
    - lp1964400-lp1964686-When-resending-a-UDP-request-insert-the-query-to-the
    - lp1964400-lp1964686-Add-digdelv-system-test-to-check-timed-out-result-fo
    - lp1964400-lp1964686-After-dig-request-errors-try-to-use-other-servers-wh
    - lp1964400-lp1964686-Add-digdelv-system-test-to-check-that-dig-tries-othe
    - lp1964400-lp1964686-Fix-dig-error-when-trying-the-next-server-after-a-TC
    - lp1964400-lp1964686-Add-various-dig-host-tests-for-TCP-UDP-socket-error-
  * Remove CVE patches fixed upstream:
    - debian/patches/CVE-2022-1183.patch
      [Included in upstream release 9.18.3]
    - debian/patches/CVE-2022-2795.patch
    - debian/patches/CVE-2022-2881.patch
    - debian/patches/CVE-2022-2906.patch
    - debian/patches/CVE-2022-3080.patch
    - debian/patches/CVE-2022-38178.patch
      [Included in upstream release 9.18.7]
    - debian/patches/CVE-2022-3094.patch
    - debian/patches/CVE-2022-3736.patch
    -...

[Chris Halse Rogers (raof)]

The verification of the Stable Release Update for bind9 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package bind9 - 1:9.18.12-0ubuntu0.22.10.1

---------------
bind9 (1:9.18.12-0ubuntu0.22.10.1) kinetic; urgency=medium

  * New upstream releases 9.18.5 - 9.18.12 (LP: #2003586)
    - Updates:
      + update-quota option
      + named -V shows supported cryptographic algorithms
    - Bug Fixes Include:
      + Fix crash when using dig with +nssearch and +tcp (LP: #1258003)
      + Fix incomplete results using dig with +nssearch (LP: #1970252)
      + CVE-2022-2795, CVE-2022-2881, CVE-2022-2906, CVE-2022-3080,
        CVE-2022-38178, CVE-2022-3094, CVE-2022-3736, CVE-2022-3924
      + Fix thread safety in dns_dispatch
      + Fix ADB quota management in resolver
      + Fix Prohibited DNS error on allow-recursion
      + Fix crash when restarting server with active statschannel connection
      + Fix use after free for catalog zone processing
      + Fix leak of dns_keyfileio_t objects
      + Fix nslookup failure to use port option when record type ANY is used
      + Fix crash on dnssec-policy zone with NSEC3 and inline-signing turned on
      + Fix inheritance when setting remote server port
      + Fix assertion error when accessing statistics channel
      + Fix rndc dumpdb -expired for stuck cache
      + Fix check for other name servers after receiving FORMERR
      + See https://bind9.readthedocs.io/en/v9_18_12/notes.html#notes-for-bind-9-18-12
        for additional bug fixes and information
  * Improve dep-8 test suite (LP: #2003584):
    - d/t/zonetest: Add dep8 test for checking the domain zone creation process
    - d/t/control: Add new test outline
  * d/bind9-doc.docs: Stop installing removed file doc/misc/options.active
  * d/p/0001-Disable-treat-warnings-as-errors-in-sphinx-build.patch: refresh to
    apply with version 9.18.8
  * Remove CVE patches fixed upstream:
    - debian/patches/CVE-2022-2795.patch
    - debian/patches/CVE-2022-2881.patch
    - debian/patches/CVE-2022-2906.patch
    - debian/patches/CVE-2022-3080.patch
    - debian/patches/CVE-2022-38178.patch
      [Included in upstream release 9.18.7]
    - debian/patches/CVE-2022-3094.patch
    - debian/patches/CVE-2022-3736.patch
    - debian/patches/CVE-2022-3924.patch
      [Included in upstream release 9.18.11]

 -- Lena Voytek <email address hidden> Wed, 08 Mar 2023 08:49:53 -0700