[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2026-46276":6},{"stargazers_count":4,"fetched_at":5},7,"2026-07-30T21:17:53.703Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":16,"duplicates":17,"related":18,"reserved_at":9,"published_at":19,"modified_at":20,"state":9,"summary":21,"references_raw":23,"kevs":30,"epss":9,"epss_history":31,"metrics":32,"affected":39},"DEBIAN-CVE-2026-46276","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 \u003C= 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)",null,[],[],[],[14],{"_key":15},"CVE-2026-46276",[],[],[],"2026-06-08T17:16:45.103Z","2026-07-09T09:00:09.368634804Z",{"cisa_kev":22,"cisa_ransomware":22,"cisa_vendor":9,"epss_severity":9,"epss_score":9,"severity":9,"severity_score":9,"severity_version":9,"severity_source":9,"severity_vector":9,"severity_status":9},false,[24],{"url":25,"sources":26,"tags":28},"https://security-tracker.debian.org/tracker/CVE-2026-46276",[27],"osv_debian",[29],"Advisory",[],[],[33],{"source":27,"cvss_v2_0":9,"cvss_v3_0":9,"cvss_v3_1":34,"cvss_v4_0":9},{"baseScore":35,"baseSeverity":9,"vectorString":36,"impactScore":37,"exploitabilityScore":38},5.5,"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",6,4.6,[40,64],{"ecosystem":41,"name":42,"vendor":43,"product":42,"cpe_part":9,"purl_type":44,"purl_namespace":43,"purl_name":42,"source":9,"versions":45},"Debian","linux","debian","deb",[46,50,51,55,58,61],{"version":47,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":9,"version_end_type":9,"fixed_in":9},"all",true,"ecosystem",{"version":47,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":9,"version_end_type":9,"fixed_in":9},{"version":52,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":53,"version_end_type":54,"fixed_in":9},"lt5_10_259_1","5.10.259-1","excluding",{"version":56,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":57,"version_end_type":54,"fixed_in":9},"lt6_1_176_1","6.1.176-1",{"version":59,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":60,"version_end_type":54,"fixed_in":9},"lt6_12_86_1","6.12.86-1",{"version":62,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":63,"version_end_type":54,"fixed_in":9},"lt7_0_4_1","7.0.4-1",{"ecosystem":41,"name":65,"vendor":43,"product":65,"cpe_part":9,"purl_type":44,"purl_namespace":43,"purl_name":65,"source":9,"versions":66},"linux-6.1",[67],{"version":68,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":69,"version_end_type":54,"fixed_in":9},"lt6_1_176_1~deb11u1","6.1.176-1~deb11u1"]