{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93139 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93139 is a vulnerability in Linux, published on 17 Sep 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-93139 and fix it if it is affected.\n\nWhat it is: CVE-2026-93139 is a vulnerability in Linux, published on 17 Sep 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-93139 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-93139/ (Markdown: https://insights.sbomify.com/CVE-2026-93139/index.md)","id":"CVE-2026-93139","markdown":"https://insights.sbomify.com/CVE-2026-93139/index.md","name":"CVE-2026-93139","record":{"aliases":["GHSA-h628-62x6-4jjj","UBUNTU-CVE-2026-93139"],"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":"none","summary":"A null pointer dereference in the AMDGPU kernel driver can cause a system crash on multi-XCC GPUs due to uninitialized array entries.","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/mes: Fix hung_queue_db_array loop limit for multi-XCC\n\nThe loop iterated only AMDGPU_MAX_MES_PIPES times, leaving entries\nuninitialized for multi-XCC GPUs. This causes null pointer dereferences\nwhen accessing arrays indexed by XCC ID \u003e= 2. Extend the loop to cover\nall XCCs (AMDGPU_MAX_MES_PIPES * num_xcc), matching other per-XCC\narrays.","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/mes: Fix hung_queue_db_array loop limit for multi-XCC","id":"CVE-2026-93139","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"udf: Mark LVID buffer as uptodate before marking it dirty","id":"CVE-2026-93140"},"packages":[],"prev":{"headline":"bpf: Fix vmlinux BTF prep race in bpf_get_btf_vmlinux","id":"CVE-2026-93138"},"products":["Linux"],"published":"2026-09-17","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-10-19","vendors":["Linux"]},"summary":"A null pointer dereference in the AMDGPU kernel driver can cause a system crash on multi-XCC GPUs due to uninitialized array entries.","url":"https://insights.sbomify.com/CVE-2026-93139/"}