{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-99147 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-99147 is a vulnerability in Linux, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-99147 and fix it if it is affected.\n\nWhat it is: CVE-2026-99147 is a vulnerability in Linux, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-99147 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-99147/ (Markdown: https://insights.sbomify.com/CVE-2026-99147/index.md)","id":"CVE-2026-99147","markdown":"https://insights.sbomify.com/CVE-2026-99147/index.md","name":"CVE-2026-99147","record":{"aliases":["AZL-111278","BELL-CVE-2026-99147","DEBIAN-CVE-2026-99147","GHSA-f9vc-r5f2-m3x9","UBUNTU-CVE-2026-99147"],"analysis":null,"analysis_generated_by":null,"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/exec: don't immediately add prelocked obj to array of locked objs\n\nWhen a contention is detected the drm_exec object grabs a reference to\nthe contended object, unlocks all other objects and pre-locks the\ncontended one before anything else.\n\nThe problem is that it is possible that this pre-locked object was about\nto be destroyed and drm_exec is now holding the last reference to it.\n\nSo we never actually see this pre-locked object again to be explicitly\nlocked and so also never reserve a slot for a dma_fence object on it.\n\nShould the driver now use drm_exec_for_each_locked_object() to add a new\nfence to all locked objects we eventually see a warning or even a\nBUG_ON() to prevent random memory corruption.\n\nFix this by keeping the prelocked object out of the array of locked objs\nuntil it was explicitly mentioned by the driver again.\n\nIf the prelocked object is never mentioned again by the driver\njust unlock and drop the reference at the end of the locking loop.","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/exec: don't immediately add prelocked obj to array of locked objs","id":"CVE-2026-99147","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"drm/amdgpu: keep the eviction fence until the last handle is closed","id":"CVE-2026-99148"},"packages":[],"prev":{"headline":"drm/i915/dmc: Add sanity check for DMC load address","id":"CVE-2026-99146"},"products":["Linux"],"published":"2026-10-28","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-28","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-99147/"}