Answer in brief
CVE-2026-46276 records a Medium severity (CVSS 5.5) vulnerability in drm/amdgpu: fix zero-size GDS range init on RDNA4. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-46276 records a Medium severity (CVSS 5.5) vulnerability in drm/amdgpu: fix zero-size GDS range init on RDNA4. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c832c346cdf9022872655be621880e0f66f4135d <1f5d33e7b0a9a2a140f46e22fb52eede323c5946 || >=c832c346cdf9022872655be621880e0f66f4135d <9bc925759c05feae7dfa9570e77131d54729c8ea || >=c832c346cdf9022872655be621880e0f66f4135d <36f9602fb22ede69fcc8b422be0cf8105bf655ad || >=c832c346cdf9022872655be621880e0f66f4135d <be0376affcafa0bbb371bb501579a825eae32281 || >=c832c346cdf9022872655be621880e0f66f4135d <0e21db1a77967bc15df662efdca8ea8a61d124ea || >=c832c346cdf9022872655be621880e0f66f4135d <30c000a49094ec568c9b51b7421f7a4a3f0b0298 || >=c832c346cdf9022872655be621880e0f66f4135d <3e26c76891ab99fa173e9c501119fbb5c9f4600f || >=c832c346cdf9022872655be621880e0f66f4135d <095a8b0ad3c3b5cdc3850d961adb8a8f735220bb | 1f5d33e7b0a9a2a140f46e22fb52eede323c5946, 9bc925759c05feae7dfa9570e77131d54729c8ea, 36f9602fb22ede69fcc8b422be0cf8105bf655ad, be0376affcafa0bbb371bb501579a825eae32281, 0e21db1a77967bc15df662efdca8ea8a61d124ea, 30c000a49094ec568c9b51b7421f7a4a3f0b0298, 3e26c76891ab99fa173e9c501119fbb5c9f4600f, 095a8b0ad3c3b5cdc3850d961adb8a8f735220bb |
| Linux/Linuxgeneric | 4.20 | Not reported |
Published upstream
Jun 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 7, 2026
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix zero-size GDS range init on RDNA4 RDNA4 (GFX 12) hardware removes the GDS, GWS, and OA on-chip memory resources. The gfx_v12_0 initialisation code correctly leaves adev->gds.gds_size, adev->gds.gws_size, and adev->gds.oa_size at zero to reflect this. amdgpu_ttm_init() unconditionally calls amdgpu_ttm_init_on_chip() for each of these resources regardless of size. When the size is zero, amdgpu_ttm_init_on_chip() forwards the call to ttm_range_man_init(), which calls drm_mm_init(mm, 0, 0). drm_mm_init() immediately fires DRM_MM_BUG_ON(start + size <= start) -- trivially true when size is zero -- crashing the kernel during modprobe of amdgpu on an RX 9070 XT. Guard against this by returning 0 early from amdgpu_ttm_init_on_chip() when size_in_page is zero. This skips TTM resource manager registration for hardware resources that are absent, without affecting any other GPU type. DRM_MM_BUG_ON() only asserts if CONFIG_DRM_DEBUG_MM is enabled in the kernel config. This is apparently rarely enabled as these chips have been in the market for over a year and this issue was only reported now. Oops-Analysis: http://oops.fenrus.org/reports/bugzilla.korg/221376/report.html (cherry picked from commit 5719ce5865279cad4fd5f01011fe037168503f2d)
Quoted source text, attributed separately from HOL analysis.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c832c346cdf9022872655be621880e0f66f4135d <1f5d33e7b0a9a2a140f46e22fb52eede323c5946 || >=c832c346cdf9022872655be621880e0f66f4135d <9bc925759c05feae7dfa9570e77131d54729c8ea || >=c832c346cdf9022872655be621880e0f66f4135d <36f9602fb22ede69fcc8b422be0cf8105bf655ad || >=c832c346cdf9022872655be621880e0f66f4135d <be0376affcafa0bbb371bb501579a825eae32281 || >=c832c346cdf9022872655be621880e0f66f4135d <0e21db1a77967bc15df662efdca8ea8a61d124ea || >=c832c346cdf9022872655be621880e0f66f4135d <30c000a49094ec568c9b51b7421f7a4a3f0b0298 || >=c832c346cdf9022872655be621880e0f66f4135d <3e26c76891ab99fa173e9c501119fbb5c9f4600f || >=c832c346cdf9022872655be621880e0f66f4135d <095a8b0ad3c3b5cdc3850d961adb8a8f735220bb | 1f5d33e7b0a9a2a140f46e22fb52eede323c5946, 9bc925759c05feae7dfa9570e77131d54729c8ea, 36f9602fb22ede69fcc8b422be0cf8105bf655ad, be0376affcafa0bbb371bb501579a825eae32281, 0e21db1a77967bc15df662efdca8ea8a61d124ea, 30c000a49094ec568c9b51b7421f7a4a3f0b0298, 3e26c76891ab99fa173e9c501119fbb5c9f4600f, 095a8b0ad3c3b5cdc3850d961adb8a8f735220bb |
| Linux/Linuxgeneric | 4.20 | Not reported |
Published upstream
Jun 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 7, 2026
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix zero-size GDS range init on RDNA4 RDNA4 (GFX 12) hardware removes the GDS, GWS, and OA on-chip memory resources. The gfx_v12_0 initialisation code correctly leaves adev->gds.gds_size, adev->gds.gws_size, and adev->gds.oa_size at zero to reflect this. amdgpu_ttm_init() unconditionally calls amdgpu_ttm_init_on_chip() for each of these resources regardless of size. When the size is zero, amdgpu_ttm_init_on_chip() forwards the call to ttm_range_man_init(), which calls drm_mm_init(mm, 0, 0). drm_mm_init() immediately fires DRM_MM_BUG_ON(start + size <= start) -- trivially true when size is zero -- crashing the kernel during modprobe of amdgpu on an RX 9070 XT. Guard against this by returning 0 early from amdgpu_ttm_init_on_chip() when size_in_page is zero. This skips TTM resource manager registration for hardware resources that are absent, without affecting any other GPU type. DRM_MM_BUG_ON() only asserts if CONFIG_DRM_DEBUG_MM is enabled in the kernel config. This is apparently rarely enabled as these chips have been in the market for over a year and this issue was only reported now. Oops-Analysis: http://oops.fenrus.org/reports/bugzilla.korg/221376/report.html (cherry picked from commit 5719ce5865279cad4fd5f01011fe037168503f2d)
Quoted source text, attributed separately from HOL analysis.