CVE-2026-74638— drm/v3d 调度器超时处理串行化漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
在 Linux 内核中，已修复以下漏洞： drm/v3d：序列化调度器超时处理程序 V3D 暴露了多个独立的硬件队列（BIN、RENDER、TFU 和 CSD），但仅有一个全局重置机制。因此，任何单个队列的超时都必須停止、重置并重新启动所有其他队列的调度器。这使得并发执行的超时处理程序变得不安全。 此前始终无法确保安全，因为驱动程序侧的锁只能覆盖驱动程序的 回调函数。调度器在该回调函数之外处理超时作业及其待处理列表，超出了驱动程序的直接控制范围。因此，由一个队列触发的全局重置仍可能与另一个正在处理自身超时的队列发生
影响版本矩阵 16
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 35e4079bf1a2570abffce6ababa631afcf8ea0e5< 5884851a096d8afcdf91f0e542bac193035183a6 |
affected |
35e4079bf1a2570abffce6ababa631afcf8ea0e5< c22a45817b9c92aa0391db60e2ed467c7e6027d7 |
affected | ||
35e4079bf1a2570abffce6ababa631afcf8ea0e5< 4da94744707b27a3ae1197bdd7127da4505dc5b1 |
affected | ||
5235b56b7e5449d990d21d78723b1a5e7bb5738e |
affected | ||
12125f7d9c15e6d8ac91d10373b2db2f17dcf767 |
affected | ||
a5f162727b91e480656da1876247a91f651f76de |
affected | ||
422a8b10ba42097a704d6909ada2956f880246f2 |
affected | ||
6.1.139< 6.2 |
affected | ||
| … +8 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-74638 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
drm/v3d: Serialize the scheduler timeout handlers
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
drm/v3d: Serialize the scheduler timeout handlers
V3D exposes several independent hardware queues (BIN, RENDER, TFU and
CSD) but has only a single, global reset. A timeout on any one queue
therefore has to stop, reset and restart the schedulers of every other
queue as well. That makes concurrent timeout handlers unsafe.
`reset_lock` was never able to make them safe, as a driver-side lock can
only cover the driver's &drm_sched_backend_ops.timedout_job callback.
The scheduler handles the timed out job and its pending list around that
callback, outside of the driver's control, so a global reset triggered
by one queue can still interfere with another queue that is in the
middle of handling a timeout of its own.
Consequently, if a reset happens in the CSD queue while a CL-intensive
application is running, the global reset stops and restarts the CL
queue's scheduler while that queue is handling a timeout of its own. As
drm_sched_stop() and drm_sched_start() subtract and add the credits of
every job sitting on the pending list of the scheduler they are called
on, and as the CL queue's handler concurrently takes its job off that
same list and puts it back, the stop and the start no longer see the
same set of jobs. The CL queue is left with more credits in flight than
its limit:
[ 327.302739] ------------[ cut here ]------------
[ 327.302744] WARNING: CPU: 2 PID: 43 at drivers/gpu/drm/scheduler/sched_main.c:102 drm_sched_run_job_work+0x238/0x4d0 [gpu_sched]
[ 327.302884] CPU: 2 UID: 0 PID: 43 Comm: kworker/u16:1 Not tainted 6.18.39-v8-16k+ #3 PREEMPT
[ 327.302889] Hardware name: Raspberry Pi 5 Model B Rev 1.0 (DT)
[ 327.302893] Workqueue: v3d_bin drm_sched_run_job_work [gpu_sched]
[ 327.302984] Call trace:
[ 327.302987] drm_sched_run_job_work+0x238/0x4d0 [gpu_sched] (P)
[ 327.302997] process_scheduled_works+0x180/0x3d0
[ 327.303010] worker_thread+0x268/0x3e8
[ 327.303016] kthread+0x140/0x250
[ 327.303022] ret_from_fork+0x10/0x20
[ 327.303031] ---[ end trace 0000000000000000 ]---
From that point on, the credit count of the CL queue is broken, causing
a complete GPU hang and UI freeze.
The DRM scheduler already provides a mechanism to serialize the timeout
handlers of different schedulers: an ordered workqueue passed as
drm_sched_init()'s @timeout_wq parameter. By default, each scheduler
queues its timeout work on the system workqueue, which runs the handlers
concurrently. Give all of the queues a shared ordered workqueue instead,
as recommended by the DRM scheduler documentation for hardware that has
distinct queues but resets globally.
来源: CVE Program / CVE List V5
CVSS Information
N/A
来源: CVE Program / CVE List V5
Vulnerability Type
N/A
来源: CVE Program / CVE List V5
受影响产品
二、漏洞 CVE-2026-74638 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-74638 的情报信息
请登录查看更多情报信息。
CVE-2026-74638 补丁与修复 (3)
同批安全公告 · Linux · 2026-08-22 · 共 150 条
| CVE-2026-74705 | 10.0 CRITICAL | UDP隧道分段潜在使用-after-free漏洞 |
| CVE-2026-74612 | 10.0 CRITICAL | Linux内核veth模块SKB长度计算漏洞 |
| CVE-2026-74608 | 9.8 CRITICAL | SMB客户端cifs_try_adding_channels函数中的释放后使用漏洞 |
| CVE-2026-74591 | 9.8 CRITICAL | Linux 内核文件映射恢复索引前重试导致漏洞 |
| CVE-2026-74611 | 9.8 CRITICAL | TLS 1.3 乐观重试消息迭代器恢复漏洞 |
| CVE-2026-74628 | 9.8 CRITICAL | Linux内核 x25 远程计时器释放后使用漏洞 |
| CVE-2026-74669 | 9.8 CRITICAL | Linux IPVS IPv4选项后重定位隧道ICMP错误 |
| CVE-2026-74597 | 9.8 CRITICAL | Linux ip6_tunnel skb2->cb[]未清除漏洞 |
| CVE-2026-74662 | 9.8 CRITICAL | Linux inet frags 定时器竞争条件漏洞 |
| CVE-2026-74587 | 9.8 CRITICAL | SCTP 缓存 ASCONF 块使用后释放漏洞 |
| CVE-2026-74688 | 9.8 CRITICAL | SCTP传输控制块移除漏洞 |
| CVE-2026-74723 | 9.8 CRITICAL | btrfs LZO拒绝无有效头部的内联扩展 |
| CVE-2026-74730 | 9.8 CRITICAL | NFS：在FREE_STATEID调用期间锁定struct nfs_server |
| CVE-2026-74617 | 9.8 CRITICAL | dibs: 在dibs_dev_alloc()中初始化dibs->lock |
| CVE-2026-74727 | 9.8 CRITICAL | OpenVPN by_id移除后跳过哈希重构 |
| CVE-2026-74586 | 9.8 CRITICAL | Linux内核SCTP对等端移除时传输未清理漏洞 |
| CVE-2026-74616 | 9.8 CRITICAL | Linux内核XDP克隆数据包越界漏洞 |
| CVE-2026-74588 | 9.8 CRITICAL | Linux SCTP传输列表不同步漏洞 |
| CVE-2026-74712 | 9.3 CRITICAL | mlx5 vdpa 在 create_direct_keys() 中缓冲区长度修复漏洞 |
| CVE-2026-74665 | 9.1 CRITICAL | NET skb长度计算通用XDP片段调整后修复 |
显示前 20 条，共 150 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-74638
暂无评论