# CVE-2026-74638: drm/v3d: Serialize the scheduler timeout handlers

CVE-2026-74638 is fixed in 16 products on 1 platform, first by DEBIAN-CVE-2026-74638, released September 4, 2026. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2026-74638
- Priority: Routine
- CVSS: 4.7 (Moderate)
- EPSS: 0.0017
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Aug 22, 2026
- Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-74638

## 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.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | dtb-aarch64 opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 |
| Linux | kernel-64kb opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 |
| Linux | kernel-64kb sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 |
| Linux | kernel-64kb sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 |
| Linux | kernel-azure opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 |
| Linux | kernel-azure sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 |
| Linux | kernel-azure sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 |
| Linux | kernel-default opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 |
| Linux | kernel-default sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 |
| Linux | kernel-default sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24197-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24197-1.md) | Nov 7, 2026 |
| Linux | kernel-default-base opensuse-leap 16.0 | 6.12.0-160000.39.1.160000.2.25 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 |
| Linux | kernel-default-base sles 15.7 | 6.4.0-150700.53.84.1.150700.17.47.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 |
| Linux | kernel-default-base sles 16.0 | 6.12.0-160000.39.1.160000.2.26 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 |
| Linux | kernel-docs opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 |
| Linux | kernel-docs sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 |
| Linux | kernel-docs sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 |
| Linux | kernel-kvmsmall opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 |
| Linux | kernel-kvmsmall sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 |
| Linux | kernel-livepatch-SLE15-SP7-RT_Update_21 sles 15.7 | 1-150700.1.3.1 | [SUSE-SU-2026:4640-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4640-1.md) | Nov 7, 2026 |
| Linux | kernel-livepatch-SLE15-SP7_Update_22 sles 15.7 | 1-150700.15.3.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 |
| Linux | kernel-obs-build opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 |
| Linux | kernel-obs-build sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 |
| Linux | kernel-obs-qa opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 |
| Linux | kernel-obs-qa sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 |
| Linux | kernel-rt opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 |
| Linux | kernel-source opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 |
| Linux | kernel-source sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 |
| Linux | kernel-source sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 |
| Linux | kernel-syms opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 |
| Linux | kernel-syms sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 |
| Linux | kernel-syms sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 |
| Linux | kernel-zfcpdump opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 |
| Linux | kernel-zfcpdump sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 |
| Linux | kernel-zfcpdump sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 |
| Linux | linux Debian 14 | 7.1.9-1 | [DEBIAN-CVE-2026-74638](https://patchblox.com/security/data/fix/linux/debian-cve-2026-74638.md) | Sep 4, 2026 |

---

Data as of 2026-11-09T13:31:49Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.
