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

Goal: 1000 CNY · Raised: 1110 CNY

100%

CVE-2026-23469— drm/imagination: Synchronize interrupts before suspending the GPU

AI Predicted 5.5 Difficulty: Moderate EPSS 0.02% · P7

Possible ATT&CK Techniques 1AI

T1055 · Process Injection

Affected Version Matrix 8

VendorProductVersion RangeStatus
LinuxLinuxcc1aeedb98ad347c06ff59e991b2f94dfb4c565d< 772f3653eef50ea7cf721b05d8e275f93bc460f3affected
cc1aeedb98ad347c06ff59e991b2f94dfb4c565d< 8e0c15e426a056b9fb604cf87a1dfdec4d61e407affected
cc1aeedb98ad347c06ff59e991b2f94dfb4c565d< 2d7f05cddf4c268cc36256a2476946041dbdd36daffected
6.8affected
< 6.8unaffected
6.18.20≤ 6.18.*unaffected
6.19.10≤ 6.19.*unaffected
7.0≤ *unaffected
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2026-23469

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/imagination: Synchronize interrupts before suspending the GPU
Source: NVD (National Vulnerability Database)
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: drm/imagination: Synchronize interrupts before suspending the GPU The runtime PM suspend callback doesn't know whether the IRQ handler is in progress on a different CPU core and doesn't wait for it to finish. Depending on timing, the IRQ handler could be running while the GPU is suspended, leading to kernel crashes when trying to access GPU registers. See example signature below. In a power off sequence initiated by the runtime PM suspend callback, wait for any IRQ handlers in progress on other CPU cores to finish, by calling synchronize_irq(). At the same time, remove the runtime PM resume/put calls in the threaded IRQ handler. On top of not being the right approach to begin with, and being at the wrong place as they should have wrapped all GPU register accesses, the driver would hit a deadlock between synchronize_irq() being called from a runtime PM suspend callback, holding the device power lock, and the resume callback requiring the same. Example crash signature on a TI AM68 SK platform: [ 337.241218] SError Interrupt on CPU0, code 0x00000000bf000000 -- SError [ 337.241239] CPU: 0 UID: 0 PID: 112 Comm: irq/234-gpu Tainted: G M 6.17.7-B2C-00005-g9c7bbe4ea16c #2 PREEMPT [ 337.241246] Tainted: [M]=MACHINE_CHECK [ 337.241249] Hardware name: Texas Instruments AM68 SK (DT) [ 337.241252] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 337.241256] pc : pvr_riscv_irq_pending+0xc/0x24 [ 337.241277] lr : pvr_device_irq_thread_handler+0x64/0x310 [ 337.241282] sp : ffff800085b0bd30 [ 337.241284] x29: ffff800085b0bd50 x28: ffff0008070d9eab x27: ffff800083a5ce10 [ 337.241291] x26: ffff000806e48f80 x25: ffff0008070d9eac x24: 0000000000000000 [ 337.241296] x23: ffff0008068e9bf0 x22: ffff0008068e9bd0 x21: ffff800085b0bd30 [ 337.241301] x20: ffff0008070d9e00 x19: ffff0008068e9000 x18: 0000000000000001 [ 337.241305] x17: 637365645f656c70 x16: 0000000000000000 x15: ffff000b7df9ff40 [ 337.241310] x14: 0000a585fe3c0d0e x13: 000000999704f060 x12: 000000000002771a [ 337.241314] x11: 00000000000000c0 x10: 0000000000000af0 x9 : ffff800085b0bd00 [ 337.241318] x8 : ffff0008071175d0 x7 : 000000000000b955 x6 : 0000000000000003 [ 337.241323] x5 : 0000000000000000 x4 : 0000000000000002 x3 : 0000000000000000 [ 337.241327] x2 : ffff800080e39d20 x1 : ffff800080e3fc48 x0 : 0000000000000000 [ 337.241333] Kernel panic - not syncing: Asynchronous SError Interrupt [ 337.241337] CPU: 0 UID: 0 PID: 112 Comm: irq/234-gpu Tainted: G M 6.17.7-B2C-00005-g9c7bbe4ea16c #2 PREEMPT [ 337.241342] Tainted: [M]=MACHINE_CHECK [ 337.241343] Hardware name: Texas Instruments AM68 SK (DT) [ 337.241345] Call trace: [ 337.241348] show_stack+0x18/0x24 (C) [ 337.241357] dump_stack_lvl+0x60/0x80 [ 337.241364] dump_stack+0x18/0x24 [ 337.241368] vpanic+0x124/0x2ec [ 337.241373] abort+0x0/0x4 [ 337.241377] add_taint+0x0/0xbc [ 337.241384] arm64_serror_panic+0x70/0x80 [ 337.241389] do_serror+0x3c/0x74 [ 337.241392] el1h_64_error_handler+0x30/0x48 [ 337.241400] el1h_64_error+0x6c/0x70 [ 337.241404] pvr_riscv_irq_pending+0xc/0x24 (P) [ 337.241410] irq_thread_fn+0x2c/0xb0 [ 337.241416] irq_thread+0x170/0x334 [ 337.241421] kthread+0x12c/0x210 [ 337.241428] ret_from_fork+0x10/0x20 [ 337.241434] SMP: stopping secondary CPUs [ 337.241451] Kernel Offset: disabled [ 337.241453] CPU features: 0x040000,02002800,20002001,0400421b [ 337.241456] Memory Limit: none [ 337.457921] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]---
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
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存在安全漏洞,该漏洞源于缺少中断同步,可能导致内核崩溃。
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 cc1aeedb98ad347c06ff59e991b2f94dfb4c565d ~ 772f3653eef50ea7cf721b05d8e275f93bc460f3 -
LinuxLinux 6.8 -

II. Public POCs for CVE-2026-23469

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-23469

登录查看更多情报信息。

Same Patch Batch · Linux · 2026-04-03 · 72 CVEs total

CVE-2026-234509.8 CRITICALnet/smc: fix NULL dereference and UAF in smc_tcp_syn_recv_sock()
CVE-2026-314029.8 CRITICALnfsd: fix heap overflow in NFSv4.0 LOCK replay cache
CVE-2026-234279.8 CRITICALksmbd: fix use-after-free in durable v2 replay of active file handles
CVE-2026-234289.8 CRITICALksmbd: fix use-after-free of share_conf in compound request
CVE-2026-234559.1 CRITICALnetfilter: nf_conntrack_h323: check for zero length in DecodeQ931()
CVE-2026-234618.8 HIGHBluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user
CVE-2026-234628.8 HIGHBluetooth: HIDP: Fix possible UAF
CVE-2026-234258.8 HIGHKVM: arm64: Fix ID register initialization for non-protected pKVM guests
CVE-2026-234578.6 HIGHnetfilter: nf_conntrack_sip: fix Content-Length u32 truncation in sip_help_tcp()
CVE-2026-234568.2 HIGHnetfilter: nf_conntrack_h323: fix OOB read in decode_int() CONS case
CVE-2026-234598.2 HIGHip_tunnel: adapt iptunnel_xmit_stats() to NETDEV_PCPU_STAT_DSTATS
CVE-2026-313938.1 HIGHBluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access
CVE-2026-313928.1 HIGHsmb: client: fix krb5 mount with username option
CVE-2026-314037.8 HIGHNFSD: Hold net reference for the lifetime of /proc/fs/nfs/exports fd
CVE-2026-313897.8 HIGHspi: fix use-after-free on controller registration failure
CVE-2026-234377.8 HIGHnet: shaper: protect late read accesses to the hierarchy
CVE-2026-234587.8 HIGHnetfilter: ctnetlink: fix use-after-free in ctnetlink_dump_exp_ct()
CVE-2026-234447.8 HIGHwifi: mac80211: always free skb on ieee80211_tx_prepare_skb() failure
CVE-2026-234457.8 HIGHigc: fix page fault in XDP TX timestamps handling
CVE-2026-234497.8 HIGHnet/sched: teql: Fix double-free in teql_master_xmit

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

IV. Related Vulnerabilities

V. Comments for CVE-2026-23469

No comments yet


Leave a comment