{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-99095 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-99095 is a vulnerability in Linux, published on 26 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-99095 and fix it if it is affected.\n\nWhat it is: CVE-2026-99095 is a vulnerability in Linux, published on 26 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-99095 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-99095/ (Markdown: https://insights.sbomify.com/CVE-2026-99095/index.md)","id":"CVE-2026-99095","markdown":"https://insights.sbomify.com/CVE-2026-99095/index.md","name":"CVE-2026-99095","record":{"aliases":["AZL-111128","BELL-CVE-2026-99095","DEBIAN-CVE-2026-99095","GHSA-v4rc-4368-fvrr","UBUNTU-CVE-2026-99095"],"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/vc4: drain the hangcheck timer and works on V3D unbind\n\nNothing stops the hangcheck timer that submitted jobs arm, or the\njob_done_work that the render-done interrupt queues, at teardown:\nvc4_irq_disable() cancels only overflow_mem_work, and vc4_gem_destroy()\nruns from the drm-managed release, after vc4_v3d_unbind() has already\nuninstalled the V3D interrupt and cleared vc4-\u003ev3d. A timer still armed\nby then reads V3D registers through the NULL vc4-\u003ev3d pointer, and the\nlate callbacks run on the vc4_dev embedding them after it has been\nfreed.\n\nDrain them in vc4_v3d_unbind(): shut the timer down and cancel\nreset_work before the interrupt is taken down, because its\nvc4_irq_reset() re-enables it, then flush job_done_work so that\ncompletions queued at teardown still release their jobs.\n\nThis issue was found by an in-house static analysis tool.","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/vc4: drain the hangcheck timer and works on V3D unbind","id":"CVE-2026-99095","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"io_uring/register: don't exempt disabled rings from task restrictions","id":"CVE-2026-99096"},"packages":[],"prev":{"headline":"Bluetooth: btintel_pcie: fix TX descriptor bounds check","id":"CVE-2026-99094"},"products":["Linux"],"published":"2026-10-26","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-26","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-99095/"}