{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-63907 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-63907 is an 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-63907 and fix it if it is affected.\n\nWhat it is: CVE-2026-63907 is an 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-63907 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-63907/ (Markdown: https://insights.sbomify.com/CVE-2026-63907/index.md)","id":"CVE-2026-63907","markdown":"https://insights.sbomify.com/CVE-2026-63907/index.md","name":"CVE-2026-63907","record":{"aliases":["DEBIAN-CVE-2026-63907","GHSA-g9q5-69g8-2q3f","UBUNTU-CVE-2026-63907"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"high_privilege","summary":"A double free vulnerability in the Linux kernel's uio_pci_generic_sva driver allows local attackers to cause a denial of service or potentially execute code.","user_interaction":"not_required","vuln_class":"use_after_free"},"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\nuio: uio_pci_generic_sva: fix double free of devm_kzalloc() memory\n\nuio_pci_sva allocates struct uio_pci_sva_dev with devm_kzalloc() in\nprobe(), but then calls kfree(udev) both on the probe() error path\n(label out_free) and again in remove().\n\nBecause devm_kzalloc() allocations are devres-managed and are freed\nautomatically when the device is detached (including after a failing\nprobe() and during driver unbind), the explicit kfree() can lead to a\ndouble free.\n\nIf probe() fails after devm_kzalloc(), the error path frees udev and\ndevres cleanup will free it again when the core unwinds the partially\nbound device. On normal driver removal, remove() frees udev and devres\nwill free it again when the device is detached.\n\nThis issue was identified by a static analysis tool I developed and\nconfirmed by manual review. Fix by removing the manual kfree() calls\nand dropping the now-unused label.","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":"uio: uio_pci_generic_sva: fix double free of devm_kzalloc() memory","id":"CVE-2026-63907","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":"Input: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem","id":"CVE-2026-63908"},"packages":[],"prev":{"headline":"usb: musb: omap2430: Fix use-after-free in omap2430_probe()","id":"CVE-2026-63906"},"products":["Linux"],"published":"2026-07-19","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-07-19","vendors":["Linux"]},"summary":"A double free vulnerability in the Linux kernel's uio_pci_generic_sva driver allows local attackers to cause a denial of service or potentially execute code.","url":"https://insights.sbomify.com/CVE-2026-63907/"}