BIRD 3.3.0 crashes on "birdc show route for 209.24.0.0/24"
Hello all, unfortunately, BIRD 3.3.0 as shipped by EPEL 9 crashes at the following: $ birdc show route for 209.24.0.0/24 BIRD 3.3.0 ready. Connection closed by server $ Jun 9 18:34:47 kernel: bird[17874]: segfault at 0 ip 0000562a987ed574 sp 00007ffed8687a30 error 4 in bird[562a987a1000+11d000] likely on CPU 18 (core 2, socket 0) Jun 9 18:34:52 systemd-coredump[17976]: Process 17874 (bird) of user 990 dumped core.#012#012Stack trace of thread 17874:#012#0 0x0000562a987ed574 rt_show_net (/usr/sbin/bird + 0x61574)#012#012Stack trace of thread 17876:#012#0 0x00007f18d1f032cf n/a (n/a + 0x0) #012ELF object binary architecture: AMD x86-64 Jun 9 18:34:52 systemd[1]: bird.service: Main process exited, code=dumped, status=11/SEGV The correct answer of above command should be "Network not found", which it is on at least BIRD 2.16. Btw, "birdc show route 209.24.0.0/24 filtered" crashes the same way on BIRD 3.3.0. The correct answer would also be "Network not found". But as "birdc show route for 1.1.1.1" and "birdc show route for 1.1.1.0/24" both work fine, this only seems to affect non-existing routes? Do you need anything else for debugging? Regards, Robert
On 9.06.2026 at 18:44, Robert Scheck wrote:
Hello all,
unfortunately, BIRD 3.3.0 as shipped by EPEL 9 crashes at the following:
$ birdc show route for 209.24.0.0/24 BIRD 3.3.0 ready. Connection closed by server $
Jun 9 18:34:47 kernel: bird[17874]: segfault at 0 ip 0000562a987ed574 sp 00007ffed8687a30 error 4 in bird[562a987a1000+11d000] likely on CPU 18 (core 2, socket 0) Jun 9 18:34:52 systemd-coredump[17976]: Process 17874 (bird) of user 990 dumped core.#012#012Stack trace of thread 17874:#012#0 0x0000562a987ed574 rt_show_net (/usr/sbin/bird + 0x61574)#012#012Stack trace of thread 17876:#012#0 0x00007f18d1f032cf n/a (n/a + 0x0) #012ELF object binary architecture: AMD x86-64 Jun 9 18:34:52 systemd[1]: bird.service: Main process exited, code=dumped, status=11/SEGV
The correct answer of above command should be "Network not found", which it is on at least BIRD 2.16.
Btw, "birdc show route 209.24.0.0/24 filtered" crashes the same way on BIRD 3.3.0. The correct answer would also be "Network not found".
But as "birdc show route for 1.1.1.1" and "birdc show route for 1.1.1.0/24" both work fine, this only seems to affect non-existing routes?
Do you need anything else for debugging?
Regards, Robert Thanks for the heads up.
I can confirm that a FreeBSD build of BIRD 3.3.0 also crashes in this scenario. -- Marek Zarychta
Hello all, On Tue, Jun 09, 2026 at 07:28:39PM +0200, Marek Zarychta via Bird-users wrote:
unfortunately, BIRD 3.3.0 as shipped by EPEL 9 crashes at the following:
$ birdc show route for 209.24.0.0/24 BIRD 3.3.0 ready. Connection closed by server
The correct answer of above command should be "Network not found", which it is on at least BIRD 2.16.
Btw, "birdc show route 209.24.0.0/24 filtered" crashes the same way on BIRD 3.3.0. The correct answer would also be "Network not found".
That looks like a stupid oversight of myself. Unfortunately we have closed the merge window for 3.3.1 yesterday. We'll fix this in 3.3.2.
Jun 9 18:34:52 systemd[1]: bird.service: Main process exited, code=dumped, status=11/SEGV
But as "birdc show route for 1.1.1.1" and "birdc show route for 1.1.1.0/24" both work fine, this only seems to affect non-existing routes?
Do you need anything else for debugging?
Probably nothing, I already have my suspicions.
I can confirm that a FreeBSD build of BIRD 3.3.0 also crashes in this scenario.
This confirms to me that it's a straightforward bug in the logic, nothing crazy. Thank you for the report. I should have spotted this! -- Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.
Hi, just so you know, this issue has been fixed by the following one-liner: https://gitlab.nic.cz/labs/bird/-/commit/d1306a8d71aec820c672620fde70d5af4e3... It will be included in the next patch version v3.3.2. Sorry for the oversight and happy routing! David David Petera (he/him) | BIRD Tech Support | CZ.NIC, z.s.p.o. On 6/9/26 18:44, Robert Scheck wrote:
Hello all,
unfortunately, BIRD 3.3.0 as shipped by EPEL 9 crashes at the following:
$ birdc show route for 209.24.0.0/24 BIRD 3.3.0 ready. Connection closed by server $
Jun 9 18:34:47 kernel: bird[17874]: segfault at 0 ip 0000562a987ed574 sp 00007ffed8687a30 error 4 in bird[562a987a1000+11d000] likely on CPU 18 (core 2, socket 0) Jun 9 18:34:52 systemd-coredump[17976]: Process 17874 (bird) of user 990 dumped core.#012#012Stack trace of thread 17874:#012#0 0x0000562a987ed574 rt_show_net (/usr/sbin/bird + 0x61574)#012#012Stack trace of thread 17876:#012#0 0x00007f18d1f032cf n/a (n/a + 0x0) #012ELF object binary architecture: AMD x86-64 Jun 9 18:34:52 systemd[1]: bird.service: Main process exited, code=dumped, status=11/SEGV
The correct answer of above command should be "Network not found", which it is on at least BIRD 2.16.
Btw, "birdc show route 209.24.0.0/24 filtered" crashes the same way on BIRD 3.3.0. The correct answer would also be "Network not found".
But as "birdc show route for 1.1.1.1" and "birdc show route for 1.1.1.0/24" both work fine, this only seems to affect non-existing routes?
Do you need anything else for debugging?
Regards, Robert
participants (4)
-
David Petera -
Marek Zarychta -
Maria Matejka -
Robert Scheck