Linux Kernel amdgpu amdgpu_bo_create_kernel uninitialized variable

Summaryinfo

A vulnerability was found in Linux Kernel. It has been declared as very critical. Affected by this issue is the function amdgpu_bo_create_kernel of the component amdgpu. The manipulation results in uninitialized variable. This vulnerability is identified as CVE-2026-53374. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability classified as very critical has been found in Linux Kernel (version now known). Affected is the function amdgpu_bo_create_kernel of the component amdgpu. The manipulation with an unknown input leads to a uninitialized variable vulnerability. CWE is classifying the issue as CWE-457. The code uses a variable that has not been initialized, leading to unpredictable or unintended results. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: zero-initialize GART table on allocation GART TLB is flushed after unmapping but not after mapping. Since amdgpu_bo_create_kernel() does not zero-initialize the buffer, when a single PTE is written the TLB may speculatively load other uninitialized entries from the same cacheline. Those garbage entries can appear valid, and a subsequent write to another PTE in the same cacheline may cause the GPU to use a stale garbage PTE from the TLB. Fix this by calling memset_io() to zero-initialize the GART table with gart_pte_flags immediately after allocation. Using AMDGPU_GEM_CREATE_VRAM_CLEARED, SDMA-based clear will not work since SDMA needs GART to be initialized to work. (cherry picked from commit d9af8263b82b6eaa60c5718e0c6631c5037e4b24)

The advisory is available at git.kernel.org. This vulnerability is traded as CVE-2026-53374 since 06/09/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 07/19/2026).

Applying the patch d9af8263b82b6eaa60c5718e0c6631c5037e4b24 is able to eliminate this problem.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-45447). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion