rtsock_msg_mbuf() bounces every sockaddr through a struct
sockaddr_storage on the stack, and only a KASSERT checks that it
fits. Without INVARIANTS, a larger sockaddr overflows the stack.
The callers pass only sockaddrs that the kernel built or checked, so
one that does not fit is a bug in the caller.
Also check at run time, as f3be7df50f0 did for rtsock_msg_buffer():
free the mbuf and return NULL, which every caller already handles
like a failed allocation.
Fixes: 92be2847e845 ("rtsock: Avoid copying uninitialized padding bytes")
MFC after: 2 weeks
Co-Authored-By: Claude Opus 5.5