Bug 2502468 (CVE-2026-63907) - CVE-2026-63907 kernel: uio: uio_pci_generic_sva: fix double free of devm_kzalloc() memory
Summary: CVE-2026-63907 kernel: uio: uio_pci_generic_sva: fix double free of devm_kzal...
Keywords:
Status: NEW
Alias: CVE-2026-63907
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-19 16:09 UTC by OSIDB Bzimport
Modified: 2026-07-21 11:01 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-07-19 16:09:45 UTC
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.

Comment 1 Mauro Matteo Cascella 2026-07-21 10:57:42 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026071945-CVE-2026-63907-709c@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.