Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: uio: uio_pci_generic_sva: fix double free of devm_kzalloc() memory uio_pci_sva allocates struct uio_pci_sva_dev with devm_kzalloc() in probe(), but then calls kfree(udev) both on the probe() error path (label out_free) and again in remove(). Because devm_kzalloc() allocations are devres-managed and are freed automatically when the device is detached (including after a failing probe() and during driver unbind), the explicit kfree() can lead to a double free. If probe() fails after devm_kzalloc(), the error path frees udev and devres cleanup will free it again when the core unwinds the partially bound device. On normal driver removal, remove() frees udev and devres will free it again when the device is detached. This issue was identified by a static analysis tool I developed and confirmed by manual review. Fix by removing the manual kfree() calls and dropping the now-unused label.
References
- https://git.kernel.org/stable/c/e344865bfca4eb37ed8d7ac5917226e49fcec7ce
- https://git.kernel.org/stable/c/f74c8696f14149d5e43cc28b015326a759c48f00
FAQ
What is CVE-2026-63907?
CVE-2026-63907 is a documented vulnerability. In the Linux kernel, the following vulnerability has been resolved: uio: uio_pci_generic_sva: fix double free of devm_kzalloc() memory uio_pci_sva allocates struct uio_pci_sva_dev with devm_kzalloc(...
How severe is CVE-2026-63907?
CVSS scoring is not yet available for CVE-2026-63907. Check NVD for updates.
Is there a patch for CVE-2026-63907?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.