Those filesystems also don't trust their input and check bounds correctly. Mounting a malicious ext* partition can trigger code execution so it's never auto mounted and shouldn't be used on removable drives. This is a really weird limitation that the other common file systems don't have
Haha - there are many graybeards who would call most of systemd kinda crazy (myself included). But let's not get derailed into the old systemd debate here :)
Not sure what system you've used, but I've never seen automounting fail to work on ext4 volumes.
That being said, basically every file system ever is vulnerable to the malicious image. Kernel drivers assume that the metadata is sane enough and mistakes are from simple bugs, not deliberate attacks.
I never said it would fail to work, I said it's a massive vulnerability.
And no, implementations of other filesystems like FAT32 and ISO 9660 consider it a security bug when a malicious image gains arbitrarily code execution. What you described is exclusively a Linux desktop problem
