{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68437 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68437 is a denial of service vulnerability in Linux, published on 12 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-68437 and fix it if it is affected.\n\nWhat it is: CVE-2026-68437 is a denial of service vulnerability in Linux, published on 12 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-68437 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-68437/ (Markdown: https://insights.sbomify.com/CVE-2026-68437/index.md)","id":"CVE-2026-68437","markdown":"https://insights.sbomify.com/CVE-2026-68437/index.md","name":"CVE-2026-68437","record":{"aliases":["BELL-CVE-2026-68437","DEBIAN-CVE-2026-68437","GHSA-xgqq-c8v8-545w","UBUNTU-CVE-2026-68437"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel GPU driver","requires_auth":"low_privilege","summary":"A logic error in the Imagination GPU driver causes kernel warnings and potential job timeouts, leading to denial of service for local users.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/imagination: Fit paired fragment job in the correct CCCB\n\nFor geometry jobs with a paired fragment job, at the moment, the\nDRM scheduler's prepare_job() callback:\n\n- checks for internal (driver) dependencies for the geometry job;\n- calls into pvr_queue_get_paired_frag_job_dep() to check for external\n  dependencies for the fragment job (the two jobs are submitted together\n  but the common scheduler code doesn't know about it, so this needs to\n  be done at this point in time);\n- calls into the prepare_job() callback again, but for the fragment job,\n  to check its internal dependencies as well, passing the fragment job's\n  drm_sched_job and the geometry job's drm_sched_entity / pvr_queue.\n\nThe problem with the last step is that pvr_queue_prepare_job() doesn't\nalways take the mismatched fragment job and geometry queue into account,\nin particular when checking whether there is space for the fragment\ncommand to be submitted, so the code ends up checking for space in the\ngeometry (i.e. wrong) CCCB.\nThe rest of the nested prepare_job() callback happens to work fine at\nthe moment as the other internal dependencies are not relevant for a\npaired fragment job.\n\nMove the initialisation of a paired fragment job's done fence and CCCB\nfence to pvr_queue_get_paired_frag_job_dep(), inferring the correct\nqueue from the fragment job itself.\n\nThis fixes cases where prepare_job() wrongly assumed that there was\nenough space for a paired fragment job in its own CCCB, unblocking\nrun_job(), which then returned early without writing the full sequence\nof commands to the CCCB.\n\nThe above lead to kernel warnings such as the following and potentially\njob timeouts (depending on waiters on the missing commands):\n\n  [  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\n  [  552.421230] Modules linked in:\n  [  552.421592] CPU: 2 UID: 0 PID: 63 Comm: kworker/u16:5 Tainted: G        W           7.0.0-rc2-gc5d053e4dccb #39 PREEMPT\n  [  552.421625] Tainted: [W]=WARN\n  [  552.421637] Hardware name: Texas Instruments AM625 SK (DT)\n  [  552.421655] Workqueue: powervr-sched drm_sched_run_job_work [gpu_sched]\n  [  552.421744] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n  [  552.421766] pc : pvr_cccb_write_command_with_header+0x2c4/0x330 [powervr]\n  [  552.421850] lr : pvr_queue_submit_job_to_cccb+0x57c/0xa74 [powervr]\n  [  552.421923] sp : ffff800084c47650\n  [  552.421936] x29: ffff800084c47740 x28: 0000000000000df8 x27: ffff800088a77000\n  [  552.421979] x26: 0000000000000030 x25: ffff800084c47680 x24: 0000000000001000\n  [  552.422017] x23: ffff800084c47820 x22: 1ffff00010988ecc x21: 0000000000000008\n  [  552.422055] x20: 0000000000000208 x19: ffff000006ad5a88 x18: 0000000000000000\n  [  552.422093] x17: 0000000020020000 x16: 0000000000020000 x15: 0000000000000000\n  [  552.422130] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000\n  [  552.422167] x11: 000000000000f2f2 x10: 00000000f3000000 x9 : 00000000f3f3f3f3\n  [  552.422204] x8 : 00000000f2f2f200 x7 : ffff700010988ecc x6 : 0000000000000008\n  [  552.422241] x5 : 0000000000000000 x4 : 1ffff0001114ee00 x3 : 0000000000000000\n  [  552.422278] x2 : 0000000000000007 x1 : 0000000000000fff x0 : 000000000000002f\n  [  552.422316] Call trace:\n  [  552.422330]  pvr_cccb_write_command_with_header+0x2c4/0x330 [powervr] (P)\n  [  552.422411]  pvr_queue_submit_job_to_cccb+0x57c/0xa74 [powervr]\n  [  552.422486]  pvr_queue_run_job+0x3a4/0x990 [powervr]\n  [  552.422562]  drm_sched_run_job_work+0x580/0xd48 [gpu_sched]\n  [  552.422623]  process_one_work+0x520/0x1288\n  [  552.422657]  worker_thread+0x3f0/0xb3c\n  [  552.422679]  kthread+0x334/0x3d8\n  [  552.422706]  ret_from_fork+0x10/0x20","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"drm/imagination: Fit paired fragment job in the correct CCCB","id":"CVE-2026-68437","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"smp: Make CSD lock acquisition atomic for debug mode","id":"CVE-2026-68438"},"packages":[],"prev":{"headline":"drm/amd/display: use kvzalloc to allocate struct dc","id":"CVE-2026-68436"},"products":["Linux"],"published":"2026-08-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A logic error in the Imagination GPU driver causes kernel warnings and potential job timeouts, leading to denial of service for local users.","url":"https://insights.sbomify.com/CVE-2026-68437/"}