[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2026-52976":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-52976","In the Linux kernel, the following vulnerability has been resolved:  drm/xe: Fix error cleanup in xe_exec_queue_create_ioctl()  Two error handling issues exist in xe_exec_queue_create_ioctl():  1. When xe_hw_engine_group_add_exec_queue() fails, the error path jumps    to put_exec_queue which skips xe_exec_queue_kill(). If the VM is in    preempt fence mode, xe_vm_add_compute_exec_queue() has already added    the queue to the VM's compute exec queue list. Skipping the kill    leaves the queue on that list, leading to a dangling pointer after    the queue is freed.  2. When xa_alloc() fails after xe_hw_engine_group_add_exec_queue() has    succeeded, the error path does not call    xe_hw_engine_group_del_exec_queue() to remove the queue from the hw    engine group list. The queue is then freed while still linked into    the hw engine group, causing a use-after-free.  Fix both by: - Changing the xe_hw_engine_group_add_exec_queue() failure path to jump   to kill_exec_queue so that xe_exec_queue_kill() properly removes the   queue from the VM's compute list. - Adding a del_hw_engine_group label before kill_exec_queue for the   xa_alloc() failure path, which removes the queue from the hw engine   group before proceeding with the rest of the cleanup.  (cherry picked from commit 37c831f401746a45d510b312b0ed7a77b1e06ec8)",null,[],[],[],[14],{"_key":15},"CVE-2026-52976",[],[],[],"2026-06-24T17:17:08.183Z","2026-06-30T00:00:14.037997119Z",{"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-52976",[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_94_1",true,"ecosystem","6.12.94-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},"lt7_0_10_1","7.0.10-1"]