https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 06:48:58 +0000 https://vulnerability.circl.lu/vuln/cve-2026-45878 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/amdkfd: Fix watch_id bounds checking in debug address watch v2</p> <p>The address watch clear code receives watch_id as an unsigned value (u32), but some helper functions were using a signed int and checked bits by shifting with watch_id.</p> <p>If a very large watch_id is passed from userspace, it can be converted to a negative value. This can cause invalid shifts and may access memory outside the watch_points array.</p> <p>drm/amdkfd: Fix watch_id bounds checking in debug address watch v2</p> <p>Fix this by checking that watch_id is within MAX_WATCH_ADDRESSES before using it. Also use BIT(watch_id) to test and clear bits safely.</p> <p>This keeps the behavior unchanged for valid watch IDs and avoids undefined behavior for invalid ones.</p> <p>Fixes the below: drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_debug.c:448 kfd_dbg_trap_clear_dev_address_watch() error: buffer overflow &#39;pdd-&gt;watch_points&#39; 4 &lt;= u32max user_rl=&#39;0-3,2147483648-u32max&#39; uncapped</p> <p>drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_debug.c 433 int kfd_dbg_trap_clear_dev_address_watch(struct kfd_process_device *pdd, 434 uint32_t watch_id) 435 { 436 int r; 437 438 if (!kfd_dbg_owns_dev_watch_id(pdd, watch_id))</p> <p>kfd_dbg_owns_dev_watch_id() doesn&#39;t check for negative values so if watch_id is larger than INT_MAX it leads to a buffer overflow. (Negative shifts are undefined).</p> <p>439 return -…</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/amdkfd: Fix watch_id bounds checking in debug address watch v2</p> <p>The address watch clear code receives watch_id as an unsigned value (u32), but some helper functions were using a signed int and checked bits by shifting with watch_id.</p> <p>If a very large watch_id is passed from userspace, it can be converted to a negative value. This can cause invalid shifts and may access memory outside the watch_points array.</p> <p>drm/amdkfd: Fix watch_id bounds checking in debug address watch v2</p> <p>Fix this by checking that watch_id is within MAX_WATCH_ADDRESSES before using it. Also use BIT(watch_id) to test and clear bits safely.</p> <p>This keeps the behavior unchanged for valid watch IDs and avoids undefined behavior for invalid ones.</p> <p>Fixes the below: drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_debug.c:448 kfd_dbg_trap_clear_dev_address_watch() error: buffer overflow &#39;pdd-&gt;watch_points&#39; 4 &lt;= u32max user_rl=&#39;0-3,2147483648-u32max&#39; uncapped</p> <p>drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_debug.c 433 int kfd_dbg_trap_clear_dev_address_watch(struct kfd_process_device *pdd, 434 uint32_t watch_id) 435 { 436 int r; 437 438 if (!kfd_dbg_owns_dev_watch_id(pdd, watch_id))</p> <p>kfd_dbg_owns_dev_watch_id() doesn&#39;t check for negative values so if watch_id is larger than INT_MAX it leads to a buffer overflow. (Negative shifts are undefined).</p> <p>439 return -…</p> https://vulnerability.circl.lu/vuln/cve-2026-45878