Bug#1112535: /usr/lib/systemd/systemd-networkd: segfault after upgrade to 257.8-1~deb13u1, no connectivity after reboot

[Kevin Otte]

Just ran headlong into this as well. I'm glad I did my workstation first 
as my VM host is running the same config and my whole network would now 
be offline had I applied it there.

I concur with raising the severity of this bug and eagerly await a fixed 
package.

On Sat, 6 Sep 2025 10:34:20 -0400 Robert Edmonds <edmonds at debian.org> wrote:
> Bjørn Mork wrote:
> > I hit this as well with the upgrade from 13.0 to 13.1.  Downgrading systemd 
> > from 257.8-1~deb13u1  to 257.7-1 again fixed the problem.  But this is very
> > hard to do without networking....
> > 
> > Which I believe justifies increasing the severity of this bug even more. It
> > completely breaks affected systems in hard to repair ways.  
> > 
> > I believe this bug might be relevant:
> > https://github.com/systemd/systemd/issues/38515
> > 
> > The failing system has a complex setup with VLANs on top of a bridge.
> 
> Hello,
> 
> I can confirm that systemd-networkd from the systemd 257.8-1~deb13u1 in
> stable crashes on configurations with VLAN-aware bridges with a similar
> stack trace to the one given in [0]. I have also seen this crash in one
> of the Debian v258 RC's.
> 
> The problem seems to be that v257.8 is missing the fix in [1] that was
> released in v257.9.
> 
> [0]: https://github.com/systemd/systemd/issues/38515
> 
> [1]: https://github.com/systemd/systemd/commit/24c1f6f5ac06b29d39d587ecccb269fd42349307
> 
> -- 
> Robert Edmonds
> edmonds at debian.org
> 
>