{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68237 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68237 is a denial of service vulnerability in Linux, published on 10 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-68237 and fix it if it is affected.\n\nWhat it is: CVE-2026-68237 is a denial of service vulnerability in Linux, published on 10 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-68237 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-68237/ (Markdown: https://insights.sbomify.com/CVE-2026-68237/index.md)","id":"CVE-2026-68237","markdown":"https://insights.sbomify.com/CVE-2026-68237/index.md","name":"CVE-2026-68237","record":{"aliases":["DEBIAN-CVE-2026-68237","GHSA-p526-pm6j-fr73","UBUNTU-CVE-2026-68237"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A local attacker can cause a system hang by triggering a GPU reset while a user queue is in a specific state, leading to a denial of service.","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/amdgpu/userq: fix indefinite fence wait during GPU reset\n\npre_reset only force-completes fences of MAPPED queues. A queue in any\nother state (e.g. mid-eviction) keeps its last_fence pending; after a\nGPU reset that fence never signals, so the eviction/suspend worker and\nprocess teardown (amdgpu_evf_mgr_flush_suspend) wait on it forever and\nwedge the machine:\n\n  INFO: task kworker/6:28 blocked for more than 120 seconds.\n  Workqueue: events amdgpu_eviction_fence_suspend_worker [amdgpu]\n  Call Trace:\n   dma_fence_wait_timeout+0x7e/0x130\n   amdgpu_userq_evict+0x67/0x140 [amdgpu]\n   amdgpu_eviction_fence_suspend_worker+0xd8/0x160 [amdgpu]\n   process_scheduled_works+0xa6/0x420\n\nForce-complete every queue's fence regardless of state. The unmap and\nmark-hung step stays gated on MAPPED, since unmapping a queue that is\nnot mapped is invalid.\n\n(cherry picked from commit 9102b39fa924dcc3dc75a3137bfa9633c40b88c0)","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/amdgpu/userq: fix indefinite fence wait during GPU reset","id":"CVE-2026-68237","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"drm/amdgpu: Release VFCT ACPI table reference","id":"CVE-2026-68238"},"packages":[],"prev":{"headline":"drm/amd/display: set new_stream to NULL after release","id":"CVE-2026-68236"},"products":["Linux"],"published":"2026-08-10","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 local attacker can cause a system hang by triggering a GPU reset while a user queue is in a specific state, leading to a denial of service.","url":"https://insights.sbomify.com/CVE-2026-68237/"}