CVE-2026-63907

uio: uio_pci_generic_sva: fix double free of devm_kzalloc() memory

Published Jul 19, 2026 CVSS 3.1 · 7.8 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability originates from a double free of memory allocated with devm_kzalloc() in the uio_pci_generic_sva driver. The driver frees this memory manually during a failed probe and again when the module is removed, but devm_kzalloc() allocations are automatically released by the device resource framework. This duplicate deallocation can corrupt the kernel heap, potentially allowing an attacker to gain arbitrary kernel execution. The flaw is a classic instance of CWE‑1341 double free.

Affected Systems

Any Linux kernel that includes the uio_pci_generic_sva driver, including all mainstream kernel releases prior to the commit that removed the manual kfree() calls. The driver is part of the ubiquitous uio subsystem, so any distribution that builds the Linux kernel with this module enabled is potentially vulnerable.

Risk and Exploitability

The damage occurs only when a process can trigger the driver’s probe or removal routines, so the most likely attack vector is local, requiring root or module load privileges to provoke the double free. The CVSS score of 7.8 indicates high severity, but the EPSS score shows a very low exploitation probability (< 1%). The vulnerability is not listed in the CISA KEV catalog, which further suggests limited known exploitation activity. A successful exploitation could lead to arbitrary code execution in the kernel.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the kernel patch that incorporates commit e344865bfca4eb37ed8d7ac5917226e49fcec7ce or f74c8696f14149d5e43cc28b015326a759c48f00 to eliminate the double free.
  • If updating the kernel is not immediately feasible, block the uio_pci_generic_sva module from loading by adding it to a module blacklist or disabling the driver in the kernel configuration.
  • Restrict privileged users from loading or probing devices that would activate the driver’s probe or removal routines, and monitor system logs for attempts to bind the driver to detect potential misuse.

Generated by OpenCVE AI on October 30, 2026 at 17:14 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8593-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8603-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8618-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8663-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8664-1 Linux kernel (NVIDIA BaseOS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-1 Linux kernel (GCP) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-3 Linux kernel (Oracle) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-415
CPEs cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc5:*:*:*:*:*:*
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
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.
Title uio: uio_pci_generic_sva: fix double free of devm_kzalloc() memory
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-1341

    Multiple Releases of Same Resource or Handle

  • CWE-415

    Double Free

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Jul 19, 2026, 2:55 PM
Reserved
Jul 19, 2026, 7:54 AM
Status
Analyzed
Published
Jul 19, 2026, 4:17 PM
Modified
Oct 30, 2026, 2:30 PM
Severity
Public date
Jul 19, 2026, 12:00 AM