CVE-2026-63907

Last refreshed2026-10-30

Status: UPDATED | Advisory ID: CVE-2026-63907

Key Details

CVE	CVE-2026-63907
CVSS Score / Version	7.8 (High) / CVSS v3.1
Updated	2026-10-30
CVSS Vector	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`
CVSS Prose	attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products	Linux Kernel
Classified as	CWE-415 (Double Free)

Vendor	Product	Affected Versions	Patch Status
Linux	Linux Kernel

Vendor

Product

Affected Versions

Patch Status

Linux

Linux Kernel

Subsystems	OT Supporting Infrastructure
Sectors	All Sectors

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. (NVD)

Monitor Linux's web page for any future patch releases.

Source	Reference
NVD	https://nvd.nist.gov/vuln/detail/CVE-2026-63907
CVE	https://www.cve.org/CVERecord?id=CVE-2026-63907

Source

Reference

NVD

CVE