{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98521 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98521 is a 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-98521 and fix it if it is affected.\n\nWhat it is: CVE-2026-98521 is a 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-98521 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-98521/ (Markdown: https://insights.sbomify.com/CVE-2026-98521/index.md)","id":"CVE-2026-98521","markdown":"https://insights.sbomify.com/CVE-2026-98521/index.md","name":"CVE-2026-98521","record":{"aliases":["AZL-109427","BELL-CVE-2026-98521","DEBIAN-CVE-2026-98521","GHSA-7hvf-3rfm-fg86","UBUNTU-CVE-2026-98521"],"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 i915 DRM driver causes an infinite loop during GEM object destruction, leading to local denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"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/i915: fix incorrect RCU teardown order\n\ni915_gem_busy_ioctl uses dma_resv_for_each_fence_unlocked() to iterate\nover the fences in an GEM object without holding a reference but only\nthe RCU read side lock.\n\nWhat can happen here is that the GEM object is destroyed concurrently\nwhile i915_gem_busy_ioctl is still running. This won't free the GEM\nobjects memory, but still drops all the dma_fence references.\n\nNow when dma_resv_for_each_fence_unlocked() sees a destroyed dma_fence it\nassumes that a new fence list was installed and re-starts the loop.\n\nBut in the case of a destroyed GEM object a new fence list is never\ninstalled, only the old one freed and therefore the iteration never\nfinishes resulting in an endless loop.\n\nThe solution is to drop the fence references only after the RCU grace\nperiod.\n\nThe fixes tag is not necessary the patch introducing the problem, but the\none making it so worse that we need to address it.\n\nThis problem was pointed out by Sashiko-bot.\n\n(cherry picked from commit 5113479556025093bf8133bb2dcaa33be2d50921)","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/i915: fix incorrect RCU teardown order","id":"CVE-2026-98521","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"drm/imagination: Propagate map failures correctly from pvr_mmu_map_sgl()","id":"CVE-2026-98522"},"packages":[],"prev":{"headline":"drm/amdkfd: fix use-after-free and multi-container gap in kfd_dev_mapping","id":"CVE-2026-98520"},"products":["Linux"],"published":"2026-10-18","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 race condition in the i915 DRM driver causes an infinite loop during GEM object destruction, leading to local denial of service.","url":"https://insights.sbomify.com/CVE-2026-98521/"}