Master is affected too.
The use of the slist pointer after it has been freed is completely wrong - it never contained information relevant for the situation. It sort of looks like copy-paste error where the name of the variable has not been updated, except with the twist that the "right variable" has never been assigned a value, either.
gcc-12 development version gives a warning (error when --enable-debug -> -Werror used) in S3_1 about load_ruleset_units() use of slist pointer at line 2468 after it has been freed at line 2442.
I did a gcc-12 build of S3_0 already, and it went through fine -> this is not affecting 3.0.0 plans.
Haven't checked situation in master yet.