Carl Henrik Lunde

The issue is related to the `udf read inode` function in the Linux kernel, which does not validate certain length values. This allows local users to cause a denial of service, resulting in incorrect data representation or integer overflow, and potentially leading to an OOPS (kernel panic) via a crafted UDF filesystem.

The issue concerns a function in the Linux kernel that does not properly validate a length value in a specific field of an iso9660 image, allowing local users to access sensitive information from kernel memory by using a crafted image.

The issue is related to the UDF filesystem implementation in the Linux kernel, which does not validate certain lengths. This allows local users to cause a denial of service, resulting in a buffer over-read and system crash, via a crafted filesystem image. The problem is associated with the files fs/udf/inode.c and fs/udf/symlink.c.

The issue allows local users to cause a denial of service, resulting in a system crash, by utilizing a crafted UDF filesystem image. This is due to the `udf pc to char` function relying on unused component lengths.

The issue is related to the UDF filesystem implementation in the Linux kernel, where it does not ensure sufficient space for storing a symlink target's name along with a trailing 0 character. This allows local users to obtain sensitive information via a crafted filesystem image, related to the fs/udf/symlink.c and fs/udf/unicode.c files.

The issue concerns a problem where a program executes in a way that alters the relationship between the setuid system call and the getresuid saved set-user-ID value. This makes it easier for local users to gain privileges by exploiting a program that mistakenly expected it could permanently drop privileges. The vulnerability may lead to a violation of confidentiality, integrity, and availability of protected information and can be exploited locally.