It's been a decade but I have previously fuzzed multiple linux file system implementations and was able panic the kernel. I would be somewhat surprised if none

It's been a decade but I have previously fuzzed multiple linux file system implementations and was able panic the kernel. I would be somewhat surprised if none had code execution vulnerabilities at some point, but I can't think of any publicly known ones off the top of my head. Of course there absolutely have been auto-run vulnerabilities too. And modern Linux desktops have more auto-running auto-indexing stuff than ever. I've absolutely seen mounted drives being eagerly explore by gnome thumbnail generation stuff and likewise. The challenge for modern security isn't avoiding vulnerabilities, it's avoiding whole classes of behavior that might be vulnerable because the attack surfaces are so huge that we'll inevitably miss vulnerabilities so long as they're not structurally impossible. So for example, I'd always prefer to interact with a potentially malicious file system via an ephemeral read-only VM that reads the files and exports a network-fs like interface to my working system... It's just too hard to be certain there are no filesystem vulnerabilities-- they have huge surfaces and they're not usually tested against that. I can't even be sure latest genius systemd feature doesn't silently run stuff on removable media (just as it did stuff like given unprivleged users the ability to modify the system time without clearly documenting the change), if it's allowed to touch it. And if there issues are I'll be thankful that the malware payload would have also had to contain a VM escape for it to compromise my system.