{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-63910 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-63910 is a high-severity use after free vulnerability in Linux, published on 19 Jul 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-63910 and fix it if it is affected.\n\nWhat it is: CVE-2026-63910 is a high-severity use after free vulnerability in Linux, published on 19 Jul 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-63910 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-63910/ (Markdown: https://insights.sbomify.com/CVE-2026-63910/index.md)","id":"CVE-2026-63910","markdown":"https://insights.sbomify.com/CVE-2026-63910/index.md","name":"CVE-2026-63910","record":{"aliases":["DEBIAN-CVE-2026-63910","GHSA-cwcv-9vv2-wx88","UBUNTU-CVE-2026-63910"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel's dma-buf tracepoint allows a use-after-free, potentially enabling local attackers to execute code or escalate privileges.","user_interaction":"not_required","vuln_class":"use_after_free"},"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\ndma-buf: fix UAF in dma_buf_fd() tracepoint\n\nOnce FD_ADD() returns, the fd is live in the file descriptor table\nand a thread sharing that table can close() it before DMA_BUF_TRACE()\nruns. The close drops the last reference, __fput() frees the dma_buf,\nand the tracepoint then dereferences dmabuf to take dmabuf-\u003ename_lock\n-- slab-use-after-free.\n\nSplit FD_ADD() back into get_unused_fd_flags() + fd_install() and\nemit the tracepoint between them. While the fdtable slot is reserved\nwith a NULL file pointer, a racing close() returns -EBADF without\nentering __fput(), so the dma_buf stays alive across the trace. Same\napproach as commit 2d76319c4cbb (\"dma-buf: fix UAF in dma_buf_put()\ntracepoint\").\n\nThis undoes the FD_ADD() conversion done in commit 34dfce523c90\n(\"dma: convert dma_buf_fd() to FD_ADD()\"); FD_ADD() has no place to\nhook the tracepoint safely.","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":"dma-buf: fix UAF in dma_buf_fd() tracepoint","id":"CVE-2026-63910","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"xfrm: iptfs: reset runtime state when cloning SAs","id":"CVE-2026-63911"},"packages":[],"prev":{"headline":"ksmbd: OOB read regression in smb_check_perm_dacl() ACE-walk loops","id":"CVE-2026-63909"},"products":["Linux"],"published":"2026-07-19","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-08-05","vendors":["Linux"]},"summary":"A race condition in the Linux kernel's dma-buf tracepoint allows a use-after-free, potentially enabling local attackers to execute code or escalate privileges.","url":"https://insights.sbomify.com/CVE-2026-63910/"}