{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68275 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68275 is a 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-68275 and fix it if it is affected.\n\nWhat it is: CVE-2026-68275 is a 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-68275 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-68275/ (Markdown: https://insights.sbomify.com/CVE-2026-68275/index.md)","id":"CVE-2026-68275","markdown":"https://insights.sbomify.com/CVE-2026-68275/index.md","name":"CVE-2026-68275","record":{"aliases":["BELL-CVE-2026-68275","DEBIAN-CVE-2026-68275","GHSA-4c3m-c328-j6mf","UBUNTU-CVE-2026-68275"],"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 with render group access can cause a kernel crash by requesting mapping info for an unmapped buffer object in the AMDGPU driver.","user_interaction":"not_required","vuln_class":"null_dereference"},"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: check amdgpu_vm_bo_find() result in GET_MAPPING_INFO\n\nThe AMDGPU_GEM_OP_GET_MAPPING_INFO path of amdgpu_gem_op_ioctl() looks\nup the bo_va for the buffer object in the caller's VM via\namdgpu_vm_bo_find(), but uses the returned pointer without checking it.\n\namdgpu_vm_bo_find() returns NULL when the BO has no bo_va in that VM,\nwhich is the normal case for a BO that has never been mapped. The result\nis fed straight into amdgpu_vm_bo_va_for_each_valid_mapping(), which\nexpands to list_for_each_entry(mapping, \u0026(bo_va)-\u003evalids, list) and\ndereferences bo_va, causing a NULL pointer dereference.\n\nThis is reachable by any process able to issue the ioctl (render group)\nsimply by requesting mapping info for an unmapped BO.\n\nReturn -ENOENT when no bo_va is found, jumping to out_exec so the\ndrm_exec context and GEM object reference are released.\n\n(cherry picked from commit 528b19377affc1cc7362a70a254c1dda793595f9)","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: check amdgpu_vm_bo_find() result in GET_MAPPING_INFO","id":"CVE-2026-68275","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"drm/amdgpu/gfx: fix cleaner shader IB buffer overflow","id":"CVE-2026-68276"},"packages":[],"prev":{"headline":"drm/xe/guc: Fix buffer overflow in steered register list allocation","id":"CVE-2026-68274"},"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 with render group access can cause a kernel crash by requesting mapping info for an unmapped buffer object in the AMDGPU driver.","url":"https://insights.sbomify.com/CVE-2026-68275/"}