This means the listening socket was created using SOCK_RAW as opposed to SOCK_STREAM or SOCK_DGRAM. Raw sockets are used for working with ICMP, doing packet sniffing, sending some types of custom TCP packets, etc. Basically anything that isn't UDP or TCP, you'll need a raw socket for.
Historically programs like `ping` and `traceroute` use raw sockets. Using raw sockets requires privilege, which is why those historically have been set-uid on Unix systems.
So is this a vulnerability in specific raw sockets applications (i.e., you could get it right in the application), or a vulnerability in the Windows kernel's TCP/IP stack that is only exploitable when there is a raw sockets application running?
Raw is a protocol type in the socket api allowing the application to send and receive arbitrary packets (e.g. not packets generated by the system's TCP implementation).
Most phones do that for you anyhow. Unless there are serious defects in the sensor that would probably mean it would fail QA even for bargain bin phones the amount of “AI” post processing that phones do these days is probably sufficient to erase any sensor fingerprint.
Even with DSLRs and RAW files you often don’t get a RAW output from the sensor all of them do their own “color science” magic and other alterations like denoising too even on the rawest of the RAW settings.
RAW files today just mean that the files are uncompressed or the least compressed since there might be some compression/downsampling happening at readout anyhow and that you get a ton of metadata that can be used by a photo editing app to better work with the image.
Well phew! Thankfully someone's still paying attention.