Yinyi Wu

The issue was addressed with improved memory handling. An app may be able to cause unexpected system termination or corrupt kernel memory.

The issue is related to an out-of-bounds write vulnerability that may allow an attacker to execute arbitrary code with kernel privileges. Apple is aware of a report that this issue may have been actively exploited. The estimated number of potentially affected devices is not specified.

The issue was addressed with improved memory handling. Processing a maliciously crafted USD file may disclose memory contents.

The issue allows an app to potentially execute arbitrary code with kernel privileges due to insufficient checks.

The issue was addressed with improved memory handling. An app may be able to execute arbitrary code with kernel privileges.

The issue involves multiple out-of-bounds write problems that have been resolved through enhanced bounds checking. A malicious application could potentially execute arbitrary code with kernel privileges.

A type confusion issue was addressed with improved memory handling. Processing maliciously crafted web content may lead to arbitrary code execution.

An out-of-bounds write issue was addressed with improved bounds checking, which may allow a malicious application to execute arbitrary code with kernel privileges.

The issue involves multiple out-of-bounds write problems that have been resolved through enhanced bounds checking. A malicious application could potentially execute arbitrary code with kernel privileges.

The issue allows an application to potentially cause unexpected system termination or write kernel memory due to an out-of-bounds write privilege escalation. This could be exploited through the `process token BindQueryStoreRegisterToMemoryList` function.

The issue involves an out-of-bounds write that has been addressed through improved input validation. This allows an application to potentially execute arbitrary code with kernel privileges.

A malicious application may be able to execute arbitrary code with kernel privileges due to an out-of-bounds write issue. This issue was addressed with improved bounds checking.