CVE-2026-63907
Last modified
CVE-2026-63907 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.19% chance of exploitation in the next 30 days.
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 3397c3cd859a2c51962ad032dcf97961d42f9db2, < e344865bfca4eb37ed8d7ac5917226e49fcec7ce; >= 3397c3cd859a2c51962ad032dcf97961d42f9db2, < f74c8696f14149d5e43cc28b015326a759c48f00 |
| Linux | Linux | 6.19 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-63907?
How severe is CVE-2026-63907?
How do I fix CVE-2026-63907?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-63901In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63902In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63903In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63904In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63905In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63906In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2026-63908In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63909In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-6391The Sentence To SEO (keywords, description and tags) plugin …6.1
- CVE-2026-63910In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63911In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63912In the Linux kernel, the following vulnerability has been re…9.8
Are you affected by CVE-2026-63907?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
