[defect]: 3.0.27 segfaults after "Received response to status check"

[uedvt359]

What type of defect/bug is this?

Crash or memory corruption (segv, abort, etc...)

How can the issue be reproduced?

After updating from 3.0.21 to 3.0.27, Freeradius dies with a segfault after receiving a response to a status check.

This seems to be the same issue reported as #5379, but for the 3.0.x branch instead of 3.2.x.

I've seen @alandekok's commit that supposedly fixes this (3448cd0), but there is no release that contains this fix - it's only in the unreleased branch.

Log output from the FreeRADIUS daemon

(3402) Sent Status-Server Id 215 from 0.0.0.0:48310 to 193.***.***.***:1812 length 70
(3402)   Message-Authenticator := 0x00
(3402)   NAS-Identifier := "Status Check 0. Are you alive?"
(3402) Marking home server 193.***.***.*** port 1812 alive
(3402) Received response to status check 3402 ID 215 (1 in current sequence)
Segmentation fault (core dumped)

Relevant log output from client utilities

No response

Backtrace from LLDB or GDB

[alandekok]

We will release 3.0.28 soon to address this, and other issues.