nday
CVE-2026-68437

drm/imagination: Fit paired fragment job in the correct CCCB

Linux / Linux

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

tags productLinux kernel product typeoperating system
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

Linux kernel
affected products in the CVE record: Linux · Linux
operating system
affected products in the CVE record: Linux · Linuxthe product type of Linux kernel in nday's product registry
stage
DIS
disclosed
cvss
no score yet

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
08-12T00:07Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

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

Original text of the CVE record (cvelist), shown as published.

Event log

+DISdisclosed

CVE record published by Linux.

src cvelist · nday , bulk import · raw
{
  "id": 439625,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-68437",
  "occurred_at": "2026-08-12T00:07:25.745Z",
  "observed_at": "2026-11-13T05:40:03.742099Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "state": "PUBLISHED",
    "date_published": "2026-08-12T00:07:25.745Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.