{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98510 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98510 is a high-severity vulnerability in Linux, published on 18 Oct 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-98510 and fix it if it is affected.\n\nWhat it is: CVE-2026-98510 is a high-severity vulnerability in Linux, published on 18 Oct 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-98510 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-98510/ (Markdown: https://insights.sbomify.com/CVE-2026-98510/index.md)","id":"CVE-2026-98510","markdown":"https://insights.sbomify.com/CVE-2026-98510/index.md","name":"CVE-2026-98510","record":{"aliases":["BELL-CVE-2026-98510","DEBIAN-CVE-2026-98510","GHSA-p8r6-wxq7-5fv3","UBUNTU-CVE-2026-98510"],"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 race condition in the Linux kernel's Xe GPU driver causes a NULL pointer dereference, leading to a system crash when shared buffer objects are evicted concurrently.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/xe/vm: nuke PTs only after unlinking contested VMAs\n\nIn xe_vm_close_and_put(), external-BO VMAs are queued on the contested\nlist for deferred destruction via xe_vma_destroy_unlocked(). However,\nxe_vm_pt_destroy() was previously invoked before processing contested\nVMAs, destroying vm-\u003ept_root while those VMAs were still linked to their\nrespective buffer objects (vm_bo-\u003elist.gpuva).\n\nIf a concurrent thread evicts one of those shared buffer objects,\nxe_bo_trigger_rebind() holding only bo-\u003eresv walks the BO's VMAs and, in\nfault mode, calls xe_vm_invalidate_vma() -\u003e xe_pt_zap_ptes(). Because\nvm-\u003ept_root[tile-\u003eid] is already NULL, dereferencing pt-\u003elevel causes a\nNULL ptr deref.\n\nFix this by deferring xe_vm_free_scratch() and xe_vm_pt_destroy() until\nafter all contested VMAs have been unlinked and destroyed.\n\nUser is reporting hitting a NULL ptr deref in xe_pt_zap_ptes(), which\ncould be explained by this race.\n\n(cherry picked from commit c2863648959489767f08892fd6e90577d2ea0b6a)","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/xe/vm: nuke PTs only after unlinking contested VMAs","id":"CVE-2026-98510","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"drm/nouveau: don't bump pin count on failed re-pin in nouveau_bo_pin_locked()","id":"CVE-2026-98511"},"packages":[],"prev":{"headline":"drm/virtio: fix memory leak of fence event on execbuffer failure","id":"CVE-2026-98509"},"products":["Linux"],"published":"2026-10-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-24","vendors":["Linux"]},"summary":"A race condition in the Linux kernel's Xe GPU driver causes a NULL pointer dereference, leading to a system crash when shared buffer objects are evicted concurrently.","url":"https://insights.sbomify.com/CVE-2026-98510/"}