# CVE-2026-63907: uio: uio_pci_generic_sva: fix double free of devm_kzalloc() memory

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

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jul 2026
- **Updated:** 19 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-63907, GHSA-g9q5-69g8-2q3f, UBUNTU-CVE-2026-63907

## What is CVE-2026-63907?

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.

### Official 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.

## Which versions are affected by CVE-2026-63907?


## How do I fix CVE-2026-63907?

Apply the vendor's patch.

## Is CVE-2026-63907 being exploited?

There is no known exploitation of CVE-2026-63907 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63907 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2026-63907 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63907/ (Markdown: https://insights.sbomify.com/CVE-2026-63907/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63907
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63907
- OSV: https://osv.dev/vulnerability/CVE-2026-63907

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63907/
Summaries are generated and may contain mistakes; the official description above is the record.