VulnerabilityPublished 12 Aug 2026Updated 9 Oct 2026

CVE-2026-68437: Linux kernel · drm/imagination: Fit paired fragment job in the correct CCCB

Affects Linux kernelSource GCVE Database

Not known to be exploited · fixed in 7.0.0-1014.14~24.04.1 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:05 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 7.0.0-1014.14~24.04.1, 7.0.0-1017.17~24.04.1, 7.0.0-1016.16~24.04.1 +11

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-xgqq-c8v8-545w

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
Ubuntu 26.04 LTSlinux`pkg:deb/ubuntu/linux?arch=source&distro=resolute`Other threats	Affected <7.0.0-38.38	Fixed in 7.0.0-38.38
Ubuntu 26.04 LTSlinux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=resolute`Other threats	Affected <7.0.0-1014.14	Fixed in 7.0.0-1014.14
Ubuntu 26.04 LTSlinux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=resolute`Other threats	Affected <7.0.0-1017.17	Fixed in 7.0.0-1017.17
Ubuntu 26.04 LTSlinux-azure-fde`pkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resolute`Other threats	Affected <7.0.0-1016.16	Fixed in 7.0.0-1016.16
Ubuntu 26.04 LTSlinux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=resolute`Other threats	Affected <7.0.0-1014.14	Fixed in 7.0.0-1014.14
Ubuntu 26.04 LTSlinux-gke`pkg:deb/ubuntu/linux-gke?arch=source&distro=resolute`Other threats	Affected <7.0.0-1008.9	Fixed in 7.0.0-1008.9

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available that corrects the handling of paired fragment jobs in the drm/imagination driver by properly initializing fences and checking the correct CCCB queue. Users should apply the official Linux kernel updates that include this fix. No additional mitigation is required beyond applying the vendor-provided patch.

Description

A vulnerability in the Linux kernel's drm/imagination driver was fixed that involved incorrect handling of paired fragment jobs in the DRM scheduler. The flaw caused the scheduler to check for space in the wrong command control circular buffer (CCCB), leading to kernel warnings and potential job timeouts. This was due to the prepare_job() callback not properly accounting for the paired fragment job's queue, resulting in incomplete command submissions. The issue has been resolved by adjusting the initialization of paired fragment job fences to correctly infer the queue from the fragment job itself.

Impact

This flaw can cause kernel warnings and potentially lead to job timeouts in the DRM scheduler, which may affect GPU job processing reliability. The issue does not indicate direct privilege escalation or code execution but can disrupt normal GPU command scheduling and execution, potentially impacting system stability or performance during graphics operations.

Summary

The Linux kernel vulnerability (CVE-2026-68437) affects the drm/imagination driver where the DRM scheduler's prepare_job() callback mishandles paired fragment jobs by checking for space in the geometry job's CCCB instead of the fragment job's CCCB. This leads to premature unblocking of run_job() without writing the full command sequence, causing kernel warnings and potential job timeouts. The fix moves the initialization of the paired fragment job's done fence and CCCB fence to pvr_queue_get_paired_frag_job_dep(), ensuring the correct queue is used based on the fragment job. This corrects the space check and prevents incomplete command submissions.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Oct 2026, 09:45 UTC

Technical details

References

Community reviews

Related threats