The UDF filesystem implementation in the Linux kernel before 3.18.2 does not ensure that space is available for storing a symlink target's name along with a trailing \0 character, which allows local users to obtain sensitive information via a crafted filesystem image, related to fs/udf/symlink.c and fs/udf/unicode.c.
https://source.android.com/security/bulletin/2017-07-01
https://github.com/torvalds/linux/commit/0e5cc9a40ada6046e6bc3bdfcd0c0d7e4b706b14
https://bugzilla.redhat.com/show_bug.cgi?id=1228220
http://www.securityfocus.com/bid/75001
http://www.openwall.com/lists/oss-security/2015/06/03/4
http://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.2
http://lists.opensuse.org/opensuse-security-announce/2015-09/msg00021.html
http://lists.opensuse.org/opensuse-security-announce/2015-09/msg00018.html
http://lists.opensuse.org/opensuse-security-announce/2015-08/msg00011.html
http://lists.opensuse.org/opensuse-security-announce/2015-07/msg00049.html
http://lists.opensuse.org/opensuse-security-announce/2015-07/msg00023.html