[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2026-45878":6},{"stargazers_count":4,"fetched_at":5},8,"2026-09-19T04:32:17.889Z",{"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-45878","In the Linux kernel, the following vulnerability has been resolved:  drm/amdkfd: Fix watch_id bounds checking in debug address watch v2  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.  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.  drm/amdkfd: Fix watch_id bounds checking in debug address watch v2  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.  This keeps the behavior unchanged for valid watch IDs and avoids undefined behavior for invalid ones.  Fixes the below: drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_debug.c:448 kfd_dbg_trap_clear_dev_address_watch() error: buffer overflow 'pdd->watch_points' 4 \u003C= u32max user_rl='0-3,2147483648-u32max' uncapped  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))  kfd_dbg_owns_dev_watch_id() doesn't check for negative values so if watch_id is larger than INT_MAX it leads to a buffer overflow. (Negative shifts are undefined).      439                 return -EINVAL;     440     441         if (!pdd->dev->kfd->shared_resources.enable_mes) {     442                 r = debug_lock_and_unmap(pdd->dev->dqm);     443                 if (r)     444                         return r;     445         }     446     447         amdgpu_gfx_off_ctrl(pdd->dev->adev, false); --> 448         pdd->watch_points[watch_id] = pdd->dev->kfd2kgd->clear_address_watch(     449                                                         pdd->dev->adev,     450                                                         watch_id);  v2: (as per, Jonathan Kim)  - Add early watch_id >= MAX_WATCH_ADDRESSES validation in the set path to    match the clear path.  - Drop the redundant bounds check in kfd_dbg_owns_dev_watch_id().",null,[],[],[],[14],{"_key":15},"CVE-2026-45878",[],[],[],"2026-05-27T14:17:01.547Z","2026-06-15T19:06:28.503326749Z",{"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-45878",[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},7.8,"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",9.8,4.6,[40],{"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,52],{"version":47,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":50,"version_end_type":51,"fixed_in":9},"lt6_12_85_1",true,"ecosystem","6.12.85-1","excluding",{"version":53,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":54,"version_end_type":51,"fixed_in":9},"lt6_18_14_1","6.18.14-1"]