{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72359 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72359 is a vulnerability in Linux, published on 15 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-72359 and fix it if it is affected.\n\nWhat it is: CVE-2026-72359 is a vulnerability in Linux, published on 15 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-72359 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-72359/ (Markdown: https://insights.sbomify.com/CVE-2026-72359/index.md)","id":"CVE-2026-72359","markdown":"https://insights.sbomify.com/CVE-2026-72359/index.md","name":"CVE-2026-72359","record":{"aliases":["DEBIAN-CVE-2026-72359","GHSA-r35w-2gcj-cx97","UBUNTU-CVE-2026-72359"],"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 trigger a kernel crash by querying memory stats for a purged buffer object in the Intel Xe GPU 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/xe: fix NPD in bo_meminfo()\n\nWhen a buffer object is purged, its ttm.resource is set to NULL via the\nTTM pipeline gutting flow. However, the BO remains in the client's\nobject list until userspace explicitly closes the GEM handle. If memory\nstats are queried during this time, accessing bo-\u003ettm.resource-\u003emem_type\nwill result in a NULL pointer dereference.\n\nFix this by safely skipping purged BOs in bo_meminfo, as they no longer\nconsume any memory.\n\nUser is getting NPD on device resume, and possible theory is that in\nbo_move(), if we need to evict something to SYSTEM to save the CCS state,\nbut the BO is marked as dontneed, this won't trigger a move but will\nnuke the pages, leaving us with a NULL bo resource. And the meminfo()\ndoesn't look ready to handle a NULL resource.\n\nv2 (Sashiko):\n - There could potentially be other cases where we might end up with a\n   NULL resource, so make this a general NULL check for now.\n\n(cherry picked from commit c9a8e7daa0afe3161111e27fd92176e608c7f186)","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: fix NPD in bo_meminfo()","id":"CVE-2026-72359","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":"drm/xe/pf: Don't attempt to process FAST_REQ or EVENT relays","id":"CVE-2026-72360"},"packages":[],"prev":{"headline":"drm/xe/pt: prevent invalid cursor access for purged BOs","id":"CVE-2026-72358"},"products":["Linux"],"published":"2026-08-15","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 trigger a kernel crash by querying memory stats for a purged buffer object in the Intel Xe GPU driver.","url":"https://insights.sbomify.com/CVE-2026-72359/"}