目标达成 感谢每一位支持者 — 我们达成了 100% 目标!

目标: 1000 元 · 已筹: 1336

100%

CVE-2026-68437— Imagination GPU 驱动 CCCB 错误导致远程代码执行漏洞

AI 预测 4.3 利用难度: 中等 EPSS 0.16% · P5

可能的 ATT&CK 技术 1AI

T1499 · Endpoint Denial of Service
获取后续新漏洞提醒登录后订阅

一、 漏洞 CVE-2026-68437 基础信息

漏洞信息

对漏洞内容有疑问?看看神龙的深度分析是否有帮助!
查看神龙十问 ↗

尽管我们使用了先进的大模型技术,但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性,但请您根据实际情况进行核实和判断。

Vulnerability Title
drm/imagination: Fit paired fragment job in the correct CCCB
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: drm/imagination: Fit paired fragment job in the correct CCCB For geometry jobs with a paired fragment job, at the moment, the DRM scheduler's prepare_job() callback: - checks for internal (driver) dependencies for the geometry job; - calls into pvr_queue_get_paired_frag_job_dep() to check for external dependencies for the fragment job (the two jobs are submitted together but the common scheduler code doesn't know about it, so this needs to be done at this point in time); - calls into the prepare_job() callback again, but for the fragment job, to check its internal dependencies as well, passing the fragment job's drm_sched_job and the geometry job's drm_sched_entity / pvr_queue. The problem with the last step is that pvr_queue_prepare_job() doesn't always take the mismatched fragment job and geometry queue into account, in particular when checking whether there is space for the fragment command to be submitted, so the code ends up checking for space in the geometry (i.e. wrong) CCCB. The rest of the nested prepare_job() callback happens to work fine at the moment as the other internal dependencies are not relevant for a paired fragment job. Move the initialisation of a paired fragment job's done fence and CCCB fence to pvr_queue_get_paired_frag_job_dep(), inferring the correct queue from the fragment job itself. This fixes cases where prepare_job() wrongly assumed that there was enough space for a paired fragment job in its own CCCB, unblocking run_job(), which then returned early without writing the full sequence of commands to the CCCB. The above lead to kernel warnings such as the following and potentially job timeouts (depending on waiters on the missing commands): [ 552.421075] WARNING: drivers/gpu/drm/imagination/pvr_cccb.c:178 at pvr_cccb_write_command_with_header+0x2c4/0x330 [powervr], CPU#2: kworker/u16:5/63 [ 552.421230] Modules linked in: [ 552.421592] CPU: 2 UID: 0 PID: 63 Comm: kworker/u16:5 Tainted: G W 7.0.0-rc2-gc5d053e4dccb #39 PREEMPT [ 552.421625] Tainted: [W]=WARN [ 552.421637] Hardware name: Texas Instruments AM625 SK (DT) [ 552.421655] Workqueue: powervr-sched drm_sched_run_job_work [gpu_sched] [ 552.421744] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 552.421766] pc : pvr_cccb_write_command_with_header+0x2c4/0x330 [powervr] [ 552.421850] lr : pvr_queue_submit_job_to_cccb+0x57c/0xa74 [powervr] [ 552.421923] sp : ffff800084c47650 [ 552.421936] x29: ffff800084c47740 x28: 0000000000000df8 x27: ffff800088a77000 [ 552.421979] x26: 0000000000000030 x25: ffff800084c47680 x24: 0000000000001000 [ 552.422017] x23: ffff800084c47820 x22: 1ffff00010988ecc x21: 0000000000000008 [ 552.422055] x20: 0000000000000208 x19: ffff000006ad5a88 x18: 0000000000000000 [ 552.422093] x17: 0000000020020000 x16: 0000000000020000 x15: 0000000000000000 [ 552.422130] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000 [ 552.422167] x11: 000000000000f2f2 x10: 00000000f3000000 x9 : 00000000f3f3f3f3 [ 552.422204] x8 : 00000000f2f2f200 x7 : ffff700010988ecc x6 : 0000000000000008 [ 552.422241] x5 : 0000000000000000 x4 : 1ffff0001114ee00 x3 : 0000000000000000 [ 552.422278] x2 : 0000000000000007 x1 : 0000000000000fff x0 : 000000000000002f [ 552.422316] Call trace: [ 552.422330] pvr_cccb_write_command_with_header+0x2c4/0x330 [powervr] (P) [ 552.422411] pvr_queue_submit_job_to_cccb+0x57c/0xa74 [powervr] [ 552.422486] pvr_queue_run_job+0x3a4/0x990 [powervr] [ 552.422562] drm_sched_run_job_work+0x580/0xd48 [gpu_sched] [ 552.422623] process_one_work+0x520/0x1288 [ 552.422657] worker_thread+0x3f0/0xb3c [ 552.422679] kthread+0x334/0x3d8 [ 552.422706] ret_from_fork+0x10/0x20
来源: CVE Program / CVE List V5
CVSS Information
N/A
来源: CVE Program / CVE List V5
Vulnerability Type
N/A
来源: CVE Program / CVE List V5

受影响产品

厂商产品影响版本CPE订阅
LinuxLinux eaf01ee5ba28b97f96a3d3eec4c5fbfb37ee4cde ~ 15a9863929206911a08b6f62de9c5da6931dbc9e -
LinuxLinux 6.8 -

二、漏洞 CVE-2026-68437 的公开POC

#POC 描述源链接神龙链接
AI 生成 POC高级

未找到公开 POC。

登录以生成 AI POC

三、漏洞 CVE-2026-68437 的情报信息

登录查看更多情报信息。

CVE-2026-68437 补丁与修复 (4)

同批安全公告 · Linux · 2026-08-12 · 共 22 条

CVE-2026-68440txgbe驱动模块EEPROM读取时存在堆溢出漏洞
CVE-2026-68429drm_dp_mst_topology_queue_probe()处理拓扑断裂漏洞
CVE-2026-68430AMDGPU 驱动无用BUG_ON()漏洞
CVE-2026-68431ksmbd 验证变换请求最小 PDU 尺寸
CVE-2026-68432VXLAN 变更链接时未要求 CAP_NET_ADMIN 权限
CVE-2026-68433libceph 回复解码越界漏洞
CVE-2026-68434serial: 8250_mid DNV/ICX-D/SNR平台空指针解引用漏洞
CVE-2026-68435LoongArch: kexec命令行查找地址空间不匹配漏洞
CVE-2026-68436AMD Display驱动结构dc分配漏洞
CVE-2026-68438SMP CSD锁获取原子化调试模式漏洞
CVE-2026-68439mt7925驱动NULL指针解引用漏洞
CVE-2026-68450btrfs 重复重定位根插入时释放映射节点漏洞
CVE-2026-68441net/sched: TC_ACT_REDIRECT 处理漏洞
CVE-2026-68442btrfs 不传播 EXTENT_FLAG_LOGGING 至分割的扩展映射
CVE-2026-68443Gigabyte Waterforce 设备IO在hid_hw_stop前未停止漏洞
CVE-2026-68444arm_ffa固件 ffa_partition_info_get()空指针解引用漏洞
CVE-2026-68445drm/vc4: 防止着色器缓冲区映射变为可写漏洞
CVE-2026-68446vmwgfx数组大小验证漏洞
CVE-2026-68447AMD amdkfd:限制v9 CRIU控制栈检查点复制到BO大小
CVE-2026-68448overlayfs copy_file_range 源文件访问控制漏洞

显示前 20 条,共 22 条。 查看全部 → →

IV. Related Vulnerabilities

V. Comments for CVE-2026-68437

暂无评论


发表评论