Jakob Pammer

A use-after-free issue, which occurs when a program continues to use a pointer after it has been freed, can lead to unexpected system termination or corruption of kernel memory.

A logic issue involving state management allows an unprivileged attacker to execute arbitrary code with root privileges.

An out-of-bounds write issue occurs due to insufficient bounds checking. Processing a maliciously crafted PDF file may lead to memory corruption, which happens when a program writes data outside the boundaries of a pre-allocated memory buffer.

An out-of-bounds write issue exists where an application can write data past the end of a defined memory buffer. This can lead to kernel memory corruption or unexpected system termination.

An out-of-bounds write issue exists where mounting a maliciously crafted disk image may cause unexpected system termination or corrupt kernel memory. This occurs due to insufficient bounds checking, which is a process of verifying that a program does not access memory outside the boundaries of a predefined buffer.

An authorization issue exists due to improper state management, which could allow an application to access sensitive user data.

A permissions issue exists where an application may be able to access user-sensitive data. This was addressed by implementing additional restrictions.

A use-after-free issue, which occurs when a program continues to use a pointer after it has been freed, was addressed with improved memory management. Mounting a maliciously crafted SMB network share may lead to system termination.

An out-of-bounds write issue exists due to insufficient bounds checking. An attacker in physical proximity may exploit this to cause a denial-of-service, which is a condition where the system becomes unavailable or crashes.