Ye Zhang

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 unexpected system termination.

A memory corruption issue exists due to improper memory handling. This flaw allows an application to cause unexpected system termination.

Improper input validation in the operating system kernel allows a malicious app to pass crafted data into a privileged system or kernel-facing interface. This can lead to kernel memory corruption, where the system's core memory is modified in an unintended way, or unexpected system termination. An attacker can exploit this by running a specially crafted app locally on a device to trigger the vulnerable code path and feed malformed inputs into the kernel, potentially resulting in a denial of service through forced reboots or privilege escalation.

An out-of-bounds read issue existed due to insufficient bounds checking. This could allow a malicious application to disclose coprocessor memory.

A permissions issue existed where an application could potentially modify protected areas of the file system. The issue was resolved by removing the vulnerable code.

The issue is related to an out-of-bounds read when applying binary of pdf content. This allows attackers to read out-of-bounds memory.

The issue is related to an out-of-bounds read when applying binary data to text in Samsung Notes. This could potentially allow local attackers to read memory.

Name of the Vulnerable Software and Affected Versions: macOS versions prior to 15.2 Description: An out-of-bounds access issue was addressed with improved bounds checking. This issue may allow an attacker to cause unexpected system termination or arbitrary code execution in DCP firmware. Recommendations: For versions prior to 15.2, update to macOS Sequoia 15.2 to resolve the issue.

The issue is related to a memory reading problem beyond the allowed range in the IOMobileFrameBuffer component of MacOs, tvOS, watchOS, iPadOS, and iOS operating systems. This may allow an attacker to compromise data integrity. An app may be able to corrupt coprocessor memory.

The issue is related to a buffer overflow in the IOMobileFrameBuffer component of MacOs, tvOS, watchOS, iPadOS, and iOS operating systems. This can allow an attacker to impact the confidentiality, integrity, and availability of protected information. An app may be able to corrupt coprocessor memory.

The issue was addressed with improved bounds checks. An attacker may be able to cause unexpected system termination or arbitrary code execution in DCP firmware.

The issue was addressed with improved bounds checks. An attacker may be able to cause unexpected system termination or arbitrary code execution in DCP firmware.

An out-of-bounds write issue was addressed with improved input validation. This issue may allow an app to cause a coprocessor crash.

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

The issue is related to improved memory handling and may allow an app to execute arbitrary code with kernel privileges. It is also associated with a buffer overflow in the Apple Neural Engine (ANE) of Mac OS, tvOS, watchOS, iOS, and iPadOS, which can lead to privilege escalation, arbitrary code execution, or denial of service.

The issue is caused by a buffer overflow in the Neural Engine component of the operating systems, allowing an app to execute arbitrary code with kernel privileges. This is due to improved memory handling.

The issue is related to a possible use-after-free (UAF) vulnerability in the `amdgpu cs pass1()` function. This vulnerability may allow an attacker to impact the confidentiality, integrity, and availability of protected information. The vulnerability is caused by the `gang size` check being outside of the chunk parsing loop, which requires resetting `i` before freeing the chunk data.

The issue was addressed with improved memory handling. Processing a maliciously crafted image may result in disclosure of process memory.

An out-of-bounds write issue was addressed with improved input validation. Processing a font file may lead to arbitrary code execution. The issue is related to the FontParser component and can allow an attacker to execute arbitrary code.

An out-of-bounds read issue was addressed with improved bounds checking. Processing a maliciously crafted image may lead to disclosure of user information.