CVE-2026-99183— Rocket 调度器查找核心槽位逻辑漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
在 Linux 内核中，以下漏洞已得到修复： accel/rocket：在查找调度器时，需遍历每一个核心槽位。 sched_to_core() 函数会遍历 rdev->cores[] 数组，范围从索引 0 到 rdev->num_cores；而 rocket_remove() 在移除每个核心时，都会将 num_cores 减一。如果解除绑定的核心不是最后一个，那么它之后的核心就会落在搜索范围之外，导致 sched_to_core() 对一个仍然处于绑定状态且正在执行任务的返回 NULL。然而，该函数的两个调用方均未
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-99183 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
accel/rocket: search every core slot when looking up a scheduler
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
accel/rocket: search every core slot when looking up a scheduler
sched_to_core() walks rdev->cores[] up to rdev->num_cores, and
rocket_remove() decrements num_cores for every core it removes. Unbind a
core that is not the last one and the cores behind it fall outside the
search, so sched_to_core() returns NULL for a core that is still bound and
still running jobs. Neither caller checks the result:
rocket_job_run(): rocket_fence_create(core), core->dev
rocket_job_timedout(): dev_err(core->dev, "NPU job timed out")
Unbinding the middle core of the three on an RK3588 while three clients are
submitting to all of them faults twice, once from the surviving core's
job queue and once from its reset work:
KASAN: null-ptr-deref in range [0x0000000000000220-0x0000000000000227]
Workqueue: fdad0000.npu drm_sched_run_job_work [gpu_sched]
pc : rocket_job_run+0x234/0x838 [rocket]
Call trace:
rocket_job_run+0x234/0x838 [rocket]
drm_sched_run_job_work+0x2cc/0xad8 [gpu_sched]
process_one_work+0x640/0x14f0
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
Workqueue: rocket-reset-2 drm_sched_job_timedout [gpu_sched]
pc : rocket_job_timedout+0xf0/0x1e0 [rocket]
Call trace:
rocket_job_timedout+0xf0/0x1e0 [rocket]
drm_sched_job_timedout+0x188/0x6a0 [gpu_sched]
Both are the third core: the workqueue names are its device and its
core->index, and it was left at slot 2 while num_cores had dropped to 2.
Search all the slots that were allocated, the way find_core_for_dev() now
does. A core that is still bound is then found, and the two callers get
the pointer they already assume they have.
This does not make unbinding one core out of several safe. An open client
keeps an entity pointing at the scheduler of the core that went away:
drm_sched reports it as not ready for every job that lands on it, and the
client waits in dma_fence_default_wait for a fence that will never signal.
Stopping the NULL dereference is what belongs in a fix; the rest wants
more thought.
来源: 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-99183 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-99183 的情报信息
请登录查看更多情报信息。
CVE-2026-99183 补丁与修复 (2)
同批安全公告 · Linux · 2026-10-28 · 共 117 条
| CVE-2026-99143 | Linux 内核 tracing 组件越界访问漏洞 | |
| CVE-2026-99129 | SELinux BPF 令牌权限检查漏洞 | |
| CVE-2026-99130 | Linux io_uring 拒绝服务漏洞 | |
| CVE-2026-99131 | XFS 文件系统权限检查绕过漏洞 | |
| CVE-2026-99133 | Linux 内核网络 IUCV 远程拒绝服务漏洞 | |
| CVE-2026-99132 | XFS xfs_sync_sb_buf 缓冲区锁竞争漏洞 | |
| CVE-2026-99134 | mac802154 数据竞争与空指针解引用漏洞 | |
| CVE-2026-99135 | dm-integrity 大标签丢弃无限循环漏洞 | |
| CVE-2026-99137 | CIFS 文件系统在无缓存句柄时更新 i_size 存在漏洞 | |
| CVE-2026-99136 | dm-crypt 竞态条件漏洞 | |
| CVE-2026-99138 | Linux TCP 协议栈 use-after-free 漏洞 | |
| CVE-2026-99140 | tracing 模块缓冲区事件时间戳修复 | |
| CVE-2026-99139 | TCP 协议栈 TCP_CONGESTION 选项后释放漏洞 | |
| CVE-2026-99141 | 内核 tracing 模块 print_graph_function_event 崩溃漏洞 | |
| CVE-2026-99142 | Tracing 组件栈容量检查缺失漏洞 | |
| CVE-2026-99154 | libiscsi 负任务索引拒绝漏洞 | |
| CVE-2026-99151 | AMD Display 驱动 NULL 指针解引用漏洞 | |
| CVE-2026-99153 | libiscsi 拒绝 PDU 验证逻辑漏洞 | |
| CVE-2026-99152 | libiscsi 管理响应任务验证绕过漏洞 | |
| CVE-2026-99150 | amdgpu 驱动程序资源管理漏洞 |
显示前 20 条，共 117 条。 查看全部 → →