Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2026-31656— drm/i915/gt: fix refcount underflow in intel_engine_park_heartbeat

CVSS 7.8 · High EPSS 0.01% · P2
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2026-31656

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
drm/i915/gt: fix refcount underflow in intel_engine_park_heartbeat
Source: NVD (National Vulnerability Database)
Vulnerability Description
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: ``` <4> [487.221889] Workqueue: i915-unordered engine_retire [i915] <4> [487.222640] RIP: 0010:refcount_warn_saturate+0x68/0xb0 ... <4> [487.222707] Call Trace: <4> [487.222711] <TASK> <4> [487.222716] intel_engine_park_heartbeat.part.0+0x6f/0x80 [i915] <4> [487.223115] intel_engine_park_heartbeat+0x25/0x40 [i915] <4> [487.223566] __engine_park+0xb9/0x650 [i915] <4> [487.223973] ____intel_wakeref_put_last+0x2e/0xb0 [i915] <4> [487.224408] __intel_wakeref_put_last+0x72/0x90 [i915] <4> [487.224797] intel_context_exit_engine+0x7c/0x80 [i915] <4> [487.225238] intel_context_exit+0xf1/0x1b0 [i915] <4> [487.225695] i915_request_retire.part.0+0x1b9/0x530 [i915] <4> [487.226178] i915_request_retire+0x1c/0x40 [i915] <4> [487.226625] engine_retire+0x122/0x180 [i915] <4> [487.227037] process_one_work+0x239/0x760 <4> [487.227060] worker_thread+0x200/0x3f0 <4> [487.227068] ? __pfx_worker_thread+0x10/0x10 <4> [487.227075] kthread+0x10d/0x150 <4> [487.227083] ? __pfx_kthread+0x10/0x10 <4> [487.227092] ret_from_fork+0x3d4/0x480 <4> [487.227099] ? __pfx_kthread+0x10/0x10 <4> [487.227107] ret_from_fork_asm+0x1a/0x30 <4> [487.227141] </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)
Source: NVD (National Vulnerability Database)
CVSS Information
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于intel_engine_park_heartbeat中引用计数下溢,可能导致释放后重用。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux 058179e72e0956a2dfe4927db6cbe5fbfb2406aa ~ 70d3e622b10092fc483e28e57b4e8c49d9cc7f68 -
LinuxLinux 5.5 -

II. Public POCs for CVE-2026-31656

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-31656

登录查看更多情报信息。

Same Patch Batch · Linux · 2026-04-24 · 138 CVEs total

CVE-2026-316379.8 CRITICALrxrpc: reject undecryptable rxkad response tickets
CVE-2026-315369.8 CRITICALsmb: server: let send_done handle a completion without IB_SEND_SIGNALED
CVE-2026-315899.8 CRITICALmm: call ->free_folio() directly in folio_unmap_invalidate()
CVE-2026-316699.8 CRITICALmptcp: fix slab-use-after-free in __inet_lookup_established
CVE-2026-316689.8 CRITICALseg6: separate dst_cache for input and output paths in seg6 lwtunnel
CVE-2026-316499.8 CRITICALnet: stmmac: fix integer underflow in chain mode
CVE-2026-316339.8 CRITICALrxrpc: Fix integer overflow in rxgk_verify_response()
CVE-2026-316079.8 CRITICALusbip: validate number_of_packets in usbip_pack_ret_submit()
CVE-2026-316089.8 CRITICALsmb: server: avoid double-free in smb_direct_free_sendmsg after smb_direct_flush_send_list
CVE-2026-316099.8 CRITICALsmb: client: avoid double-free in smbd_free_send_io() after smbd_send_batch_flush()
CVE-2026-316579.8 CRITICALbatman-adv: hold claim backbone gateways by reference
CVE-2026-316599.8 CRITICALbatman-adv: reject oversized global TT response buffers
CVE-2026-316369.1 CRITICALrxrpc: fix RESPONSE authenticator parser OOB read
CVE-2026-315888.8 HIGHKVM: x86: Use scratch field in MMIO fragment to hold small write values
CVE-2026-315708.8 HIGHcan: gw: fix OOB heap access in cgw_csum_crc8_rel()
CVE-2026-316228.8 HIGHNFC: digital: Bounds check NFC-A cascade depth in SDD response handler
CVE-2026-315588.8 HIGHLoongArch: KVM: Make kvm_get_vcpu_by_cpuid() more robust
CVE-2026-315538.8 HIGHKVM: arm64: Fix the descriptor address in __kvm_at_swap_desc()
CVE-2026-316298.8 HIGHnfc: llcp: add missing return after LLCP_CLOSED checks
CVE-2026-316118.6 HIGHksmbd: require 3 sub-authorities before reading sub_auth[2]

Showing top 20 of 138 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2026-31656

No comments yet


Leave a comment