drm/amdgpu: zero-initialize GART table on allocation
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)
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.1.175, 6.12.90, 6.18.32, 6.6.140, 7.0.9
- CVEs
- CVE-2026-53374
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 23:06 UTC · Revision 1
Source evidence
drm/amdgpu: zero-initialize GART table on allocation
core-osv · Original sourcePublished 19 Jul 2026, 10:01 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)
osv:CVE-2026-53374
Kernel
Fixed versions: 6.1.175, 6.6.140, 6.12.90, 6.18.32, 7.0.9
Complete source record
{
"id": "36fc68e14fa9d532934698078f13c760d65b131a8fd55aab10c6acd510ae08ac",
"url": "https://osv.dev/vulnerability/CVE-2026-53374",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "drm/amdgpu: zero-initialize GART table on allocation",
"summary": "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)",
"evidence": "osv:CVE-2026-53374",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.175",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.140",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.90",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.32",
"evidence": "/affected/1/ranges"
},
{
"value": "7.0.9",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2026-53374",
"aliases": [
"CVE-2026-53374"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "d38ceaf99ed015f2a0b9af3499791bd3a3daae21"
},
{
"fixed": "40df11255d71b02e20e70579f1b12b687e396e26"
},
{
"fixed": "91fbb5e635c8fb1b49e15c19da06480089ef719f"
},
{
"fixed": "8ae8b9e74bab94aab1d79f1688129bcc61c8b29a"
},
{
"fixed": "b17175d0a375b3ed5e81597dac4983fdb46e478d"
},
{
"fixed": "791941be5da125d9a1b228582bfdc300c05d05b3"
},
{
"fixed": "e6c2e6c2e1fa066968a16aca1cb66cd1bdde7741"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53374.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.2.0"
},
{
"fixed": "6.1.175"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.140"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.90"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.32"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.0.9"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53374.json"
}
}
],
"modified": "2026-10-28T02:30:32.105218099Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/40df11255d71b02e20e70579f1b12b687e396e26",
"https://git.kernel.org/stable/c/791941be5da125d9a1b228582bfdc300c05d05b3",
"https://git.kernel.org/stable/c/8ae8b9e74bab94aab1d79f1688129bcc61c8b29a",
"https://git.kernel.org/stable/c/91fbb5e635c8fb1b49e15c19da06480089ef719f",
"https://git.kernel.org/stable/c/b17175d0a375b3ed5e81597dac4983fdb46e478d",
"https://git.kernel.org/stable/c/e6c2e6c2e1fa066968a16aca1cb66cd1bdde7741",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53374.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-53374",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53374.json"
}
},
"related_cves": [
{
"value": "CVE-2026-53374",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 499218,
"published_at": "2026-07-19T10:01:58.292+00:00"
}