CVE-2026-99183: accel/rocket: search every core slot when looking up a scheduler

Published Oct 28, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

accel/rocket: search every core slot when looking up a scheduler

schedtocore() walks rdev->cores[] up to rdev->numcores, and rocketremove() decrements numcores for every core it removes. Unbind a core that is not the last one and the cores behind it fall outside the search, so schedtocore() returns NULL for a core that is still bound and still running jobs. Neither caller checks the result:

rocketjobrun(): rocketfencecreate(core), core->dev rocketjobtimedout(): deverr(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 drmschedrunjobwork [gpusched] pc : rocketjobrun+0x234/0x838 [rocket] Call trace: rocketjobrun+0x234/0x838 [rocket] drmschedrunjobwork+0x2cc/0xad8 [gpusched] processonework+0x640/0x14f0

KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] Workqueue: rocket-reset-2 drmschedjobtimedout [gpusched] pc : rocketjobtimedout+0xf0/0x1e0 [rocket] Call trace: rocketjobtimedout+0xf0/0x1e0 [rocket] drmschedjobtimedout+0x188/0x6a0 [gpusched]

Both are the third core: the workqueue names are its device and its core->index, and it was left at slot 2 while numcores had dropped to 2.

Search all the slots that were allocated, the way findcorefordev() 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: drmsched reports it as not ready for every job that lands on it, and the client waits in dmafencedefaultwait for a fence that will never signal. Stopping the NULL dereference is what belongs in a fix; the rest wants more thought.

Affected Software

1 affected component
Linux Linux kernel

Event History

Oct 28, 2026
CVE Published
via MITRE·10:35 AM
Data Sourced
via MITRE·10:35 AM
Description

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203