.so files are chmod +x in binary bundle

[dae]

Libraries (*.so and .so. files) do not require the executable bit (x) to be set in Linux.

Originally reported on https://forums.ankiweb.net/t/security-possible-privilege-escalation-due-to-file-permissions/42762

[jthulhu]

I think this is not an issue. It's not uncommon for shared objects to have the executable bit set, and distro policies about whether libraries should be packaged with the executable flag set have changed over the years (see this on the Debian mailing list). Some libraries are actually executable (for instance, glibc.so prints its version), but on some (old) Unix systems the permission flags are used to set the permissions to the memory their loaded into on mmap, so for those systems it's actually necessary for a so file to be executable (see this SO answer).