[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2026-31656":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-31656","In the Linux kernel, the following vulnerability has been resolved:  drm/i915/gt: fix refcount underflow in intel_engine_park_heartbeat  A use-after-free / refcount underflow is possible when the heartbeat worker and intel_engine_park_heartbeat() race to release the same engine->heartbeat.systole request.  The heartbeat worker reads engine->heartbeat.systole and calls i915_request_put() on it when the request is complete, but clears the pointer in a separate, non-atomic step. Concurrently, a request retirement on another CPU can drop the engine wakeref to zero, triggering __engine_park() -> intel_engine_park_heartbeat(). If the heartbeat timer is pending at that point, cancel_delayed_work() returns true and intel_engine_park_heartbeat() reads the stale non-NULL systole pointer and calls i915_request_put() on it again, causing a refcount underflow:  ``` \u003C4> [487.221889] Workqueue: i915-unordered engine_retire [i915] \u003C4> [487.222640] RIP: 0010:refcount_warn_saturate+0x68/0xb0 ... \u003C4> [487.222707] Call Trace: \u003C4> [487.222711]  \u003CTASK> \u003C4> [487.222716]  intel_engine_park_heartbeat.part.0+0x6f/0x80 [i915] \u003C4> [487.223115]  intel_engine_park_heartbeat+0x25/0x40 [i915] \u003C4> [487.223566]  __engine_park+0xb9/0x650 [i915] \u003C4> [487.223973]  ____intel_wakeref_put_last+0x2e/0xb0 [i915] \u003C4> [487.224408]  __intel_wakeref_put_last+0x72/0x90 [i915] \u003C4> [487.224797]  intel_context_exit_engine+0x7c/0x80 [i915] \u003C4> [487.225238]  intel_context_exit+0xf1/0x1b0 [i915] \u003C4> [487.225695]  i915_request_retire.part.0+0x1b9/0x530 [i915] \u003C4> [487.226178]  i915_request_retire+0x1c/0x40 [i915] \u003C4> [487.226625]  engine_retire+0x122/0x180 [i915] \u003C4> [487.227037]  process_one_work+0x239/0x760 \u003C4> [487.227060]  worker_thread+0x200/0x3f0 \u003C4> [487.227068]  ? __pfx_worker_thread+0x10/0x10 \u003C4> [487.227075]  kthread+0x10d/0x150 \u003C4> [487.227083]  ? __pfx_kthread+0x10/0x10 \u003C4> [487.227092]  ret_from_fork+0x3d4/0x480 \u003C4> [487.227099]  ? __pfx_kthread+0x10/0x10 \u003C4> [487.227107]  ret_from_fork_asm+0x1a/0x30 \u003C4> [487.227141]  \u003C/TASK> ```  Fix this by replacing the non-atomic pointer read + separate clear with xchg() in both racing paths. xchg() is a single indivisible hardware instruction that atomically reads the old pointer and writes NULL. This guarantees only one of the two concurrent callers obtains the non-NULL pointer and performs the put, the other gets NULL and skips it.  (cherry picked from commit 13238dc0ee4f9ab8dafa2cca7295736191ae2f42)",null,[],[],[],[14],{"_key":15},"CVE-2026-31656",[],[],[],"2026-04-24T15:16:45.097Z","2026-07-03T18:00:18.694355796Z",{"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-31656",[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,65],{"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,52,56,59,62],{"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":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":53,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":54,"version_end_type":55,"fixed_in":9},"lt5_10_259_1","5.10.259-1","excluding",{"version":57,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":58,"version_end_type":55,"fixed_in":9},"lt6_1_170_1","6.1.170-1",{"version":60,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":61,"version_end_type":55,"fixed_in":9},"lt6_12_85_1","6.12.85-1",{"version":63,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":64,"version_end_type":55,"fixed_in":9},"lt6_19_13_1","6.19.13-1",{"ecosystem":41,"name":66,"vendor":43,"product":66,"cpe_part":9,"purl_type":44,"purl_namespace":43,"purl_name":66,"source":9,"versions":67},"linux-6.1",[68],{"version":69,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":70,"version_end_type":55,"fixed_in":9},"lt6_1_170_1~deb11u1","6.1.170-1~deb11u1"]