CVE-2026-64332

The CVE-2026-64332 entry describes a Linux kernel vulnerability in the USB: ulpi driver where a memory leak occurs when registration fails. The root cause is that the allocated device name is not freed on early ULPI device registration failures. The remediation is to initialize the device structu...

EUVD-2022-55850

In the Linux kernel, the following vulnerability has been resolved: drivers: dio: fix possible memory leak in dioinit If deviceregister returns error, the 'dev' and name needs be freed. Add a release function, and then call putdevice in the error path, so the name is freed in kobjectcleanup and t...

CVE-2022-50857

In the Linux kernel, the following vulnerability has been resolved: rapidio: rio: fix possible name leak in rioregistermport If deviceregister returns error, the name allocated by devsetname need be freed. It should use putdevice to give up the reference in the error path, so that the name can be...

UBUNTU-CVE-2022-50702

In the Linux kernel, the following vulnerability has been resolved: vdpasim: fix possible memory leak in vdpasimnetinit and vdpasimblkinit Inject fault while probing module, if deviceregister fails in vdpasimnetinit or vdpasimblkinit, but the refcount of kobject is not decreased to 0, the name...

CVE-2023-53174 scsi: core: Fix possible memory leak if device_add() fails

In the Linux kernel, the following vulnerability has been resolved: scsi: core: Fix possible memory leak if deviceadd fails If deviceadd returns error, the name allocated by devsetname needs be freed. As the comment of deviceadd says, putdevice should be used to decrease the reference count in th...

CVE-2025-38703

CVE-2025-38703 affects the Linux kernel’s drm/xe path, specifically making dma-fences compliant with safe access rules. The issue arises when Xe frees data pointed to by dma-fences it exports (e.g., a timeline name) after a userspace submit queue is closed, which could lead to a use-after-free if...

UBUNTU-CVE-2022-49915

In the Linux kernel, the following vulnerability has been resolved: mISDN: fix possible memory leak in mISDNregisterdevice Afer commit 1fa5ae857bb1 "driver core: get rid of struct device's busid string array", the name of device is allocated dynamically, add putdevice to give up the reference, so...