Menu

Star on GitHub · 3.2k

CVE-2026-63907

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_kzall…

Published Jul 19, 2026EPSS 0.20%

Overview

CVE-2026-63907 is a known-severity vulnerability. It was published on July 19, 2026.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-63907?

CVE-2026-63907 is a known-severity vulnerability. It was published on July 19, 2026.

How severe is CVE-2026-63907?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-63907?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-63907?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-63907 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.