People hang out on public WiFi sometimes with packet sniffing and other tools to exploit people. Especially some distros don’t have X server remote display locked down.
If you want to know what is open or exploitable CVE you can run a script that discovers all CVE exploits against a machine





To answer all your questions I’d need some time, I’d have to go back to the 100s of hours of 2.5admins and security podcasts. But to clarify an exploit doesn’t have to be an open service especially if you aren’t running a firewall. Some bombard your network adapter into buffer overun etc, but network traffic is handled by the kernel stack. A good firewall drops packets instead of letting them all into the public interface and kernel TCP stack. Where CVE stuff can happen.
I’m not saying Linux can’t be hardened , but because it is user editable and not locked down like Mac, you have a lot of things people can alter (or not alter) by hand or packages that can leave you open.
There’s a reason we have AppArmor and SELinux, yet some don’t bother to use those tools.
There was something with discord? Discourse? screen sharing that used x11 forwarding, and was on by default. I want to say Ubuntu. When it was news I checked by SUSE install and thankfully its disabled by default. But also the reason Linux distros are moving to Wayland because X11 is a security problem.
Ubuntu ufw off by default https://documentation.ubuntu.com/server/how-to/security/firewalls/index.html