Hello,
I installed LibreELEC 11.0.6 on my Raspberry Pi 5 and happened to notice that my Windows gaming PC picked it up in "Network" despite WS-Discovery and Samba all being turned off on LibreELEC. While trying to figure out why this was happening, I noticed that the /usr/sbin/wsdd2 process has a strange uid of 61623.
So then I downloaded a fresh image and reinstalled from scratch. Nothing beyond the initial partition wizard, the initial setup wizard where I untick Samba, and the adding of the ssh password and enabling ssh is done, no add-ons, no configuration, no shares added, nothing. (FWIW, I verified the sha256sum at two different locations and burned the image to my SD card on a live boot of raspbian, turned off every other device on my network, and didn't turn ssh on until I had set a new password and checked the output of the commands listed in the code window below).
Sure enough, after the first reboot, the wsdd2 process spawns, with the same uid.
As you can see below, it is indeed listening on a few ports despite being turned off and has the mysterious 61623 uid which is absent in the /etc/passwd file.
LibreELECbd:~ # ps -a | grep wsdd2
375 61623 0:00 /usr/sbin/wsdd2
883 root 0:00 grep wsdd2
LibreELECbd:~ # cat /etc/passwd
systemd-timesync:x:191:191:systemd-timesync:/:/bin/false
systemd-network:x:193:193:systemd-network:/:/bin/sh
root:x:0:0:Root User:/storage:/bin/sh
nobody:x:65534:65534:Nobody:/:/bin/sh
dbus:x:81:81:System message bus:/:/bin/sh
system:x:430:430:service:/var/run/connman:/bin/sh
avahi:x:495:495:avahi-daemon:/var/run/avahi-daemon:/bin/sh
LibreELECbd:~ # ls -ahl /usr/sbin/wsdd2
-rwxr-xr-x 1 root root 38.6K Jan 27 04:18 /usr/sbin/wsdd2
LibreELECbd:~ # netstat -anp | grep -e tcp -e udp
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 648/sshd -D [listen
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1/systemd
tcp 0 0 0.0.0.0:5355 0.0.0.0:* LISTEN 375/wsdd2
tcp 0 0 127.0.0.1:9090 0.0.0.0:* LISTEN 812/kodi.bin
tcp 0 0 0.0.0.0:36666 0.0.0.0:* LISTEN 812/kodi.bin
tcp 0 0 0.0.0.0:3702 0.0.0.0:* LISTEN 375/wsdd2
tcp 0 0 192.168.1.113:22 192.168.1.249:48968 ESTABLISHED 866/0
tcp 0 0 :::22 :::* LISTEN 648/sshd -D [listen
tcp 0 0 :::111 :::* LISTEN 1/systemd
tcp 0 0 :::36666 :::* LISTEN 812/kodi.bin
udp 0 0 0.0.0.0:111 0.0.0.0:* 1/systemd
udp 0 0 0.0.0.0:62687 0.0.0.0:* 300/rpcbind
udp 0 0 0.0.0.0:5353 0.0.0.0:* 538/avahi-daemon: r
udp 0 0 0.0.0.0:5355 0.0.0.0:* 375/wsdd2
udp 0 0 127.0.0.1:9777 0.0.0.0:* 812/kodi.bin
udp 0 0 192.168.1.113:55962 192.168.1.1:53 ESTABLISHED 504/connmand
udp 0 0 0.0.0.0:40106 0.0.0.0:* 504/connmand
udp 0 0 0.0.0.0:3702 0.0.0.0:* 375/wsdd2
udp 0 0 :::111 :::* 1/systemd
udp 0 0 :::5353 :::* 538/avahi-daemon: r
udp 0 0 :::51862 :::* 300/rpcbindAll other processes are running either as root or with an account found in /etc/passwd. The only other reference I could find to this was this thread from 2023 where I noticed that wsdd2 has the same uid in OP's pasted crash log:
I was hoping others might be able to shine a light on if this is normal behavior or something of concern. If any other logs/output are required it's no problem but as stated above it's about as vanilla, out-of-the-box as you can get. 
