BIRD 3.3.0 crashes on "birdc show route for 209.24.0.0/24"

[Marek Zarychta]

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