Bug 2502188 (CVE-2026-53374) - CVE-2026-53374 kernel: drm/amdgpu: zero-initialize GART table on allocation
Summary: CVE-2026-53374 kernel: drm/amdgpu: zero-initialize GART table on allocation
Keywords:
Status: NEW
Alias: CVE-2026-53374
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-19 11:01 UTC by OSIDB Bzimport
Modified: 2026-08-20 05:22 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:55764 0 None None None 2026-08-17 16:51:25 UTC
Red Hat Product Errata RHSA-2026:55765 0 None None None 2026-08-17 15:30:05 UTC
Red Hat Product Errata RHSA-2026:57251 0 None None None 2026-08-20 05:22:28 UTC
Red Hat Product Errata RHSA-2026:57252 0 None None None 2026-08-20 05:13:20 UTC

Description OSIDB Bzimport 2026-07-19 11:01:29 UTC
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)

Comment 3 errata-xmlrpc 2026-08-17 15:30:05 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:55765 https://access.redhat.com/errata/RHSA-2026:55765

Comment 4 errata-xmlrpc 2026-08-17 16:51:24 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:55764 https://access.redhat.com/errata/RHSA-2026:55764

Comment 5 errata-xmlrpc 2026-08-20 05:13:19 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:57252 https://access.redhat.com/errata/RHSA-2026:57252

Comment 6 errata-xmlrpc 2026-08-20 05:22:27 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:57251 https://access.redhat.com/errata/RHSA-2026:57251


Note You need to log in before you can comment on or make changes to this bug.