12 matches found
SUSE CVE-2023-53753
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: fix mapping to non-allocated address Why There is an issue mapping non-allocated location of memory. It would allocate gpio registers from an array out of bounds. How Patch correct numbers of bounds for using...
CVE-2023-53753
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: fix mapping to non-allocated address Why There is an issue mapping non-allocated location of memory. It would allocate gpio registers from an array out of bounds. How Patch correct numbers of bounds for using...
DEBIAN-CVE-2023-53753
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: fix mapping to non-allocated address Why There is an issue mapping non-allocated location of memory. It would allocate gpio registers from an array out of bounds. How Patch correct numbers of bounds for using...
UBUNTU-CVE-2023-53753
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: fix mapping to non-allocated address Why There is an issue mapping non-allocated location of memory. It would allocate gpio registers from an array out of bounds. How Patch correct numbers of bounds for using...
CVE-2023-53753 drm/amd/display: fix mapping to non-allocated address
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: fix mapping to non-allocated address Why There is an issue mapping non-allocated location of memory. It would allocate gpio registers from an array out of bounds. How Patch correct numbers of bounds for using...
CVE-2023-53753
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: fix mapping to non-allocated address Why There is an issue mapping non-allocated location of memory. It would allocate gpio registers from an array out of bounds. How Patch correct numbers of bounds for using...
CVE-2023-53753 drm/amd/display: fix mapping to non-allocated address
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: fix mapping to non-allocated address Why There is an issue mapping non-allocated location of memory. It would allocate gpio registers from an array out of bounds. How Patch correct numbers of bounds for using...
CVE-2023-53753
The CVE-2023-53753 issue affects the Linux kernel DRM/AMD display path, where mapping to a non-allocated memory location could occur due to an out-of-bounds access when allocating gpio registers from an array. The root cause is incorrect bounds handling, and the patch corrects the bounds used for...
PT-2025-49483
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description The Linux kernel contains an issue related to memory mapping within the DRM/AMD/display subsystem. The problem involves mapping to a non-allocated memory location, specifically an...
Linux kernel 安全漏洞
Linux kernel is the kernel used by Linux, the open source operating system of the Linux Foundation in the United States. A security vulnerability exists in Linux kernel, which stems from out-of-bounds accesses to gpio register arrays, which could lead to memory security issues...
kernel: drm/amd/display: fix mapping to non-allocated address
An out-of-bounds array access was found in the AMD display driver in the Linux kernel. The driver allocates GPIO registers using incorrect bounds, leading to access of non-allocated memory addresses. This could cause kernel memory corruption or crashes during display initialization...
Code injection
When a particular GPIO is protected by blocking access to the corresponding GPIO resource registers, the protection can be bypassed using the corresponding banked GPIO registers instead in Snapdragon Mobile, Snapdragon Wear in version MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 425, SD 43...