46 matches found
CVE-2022-50669
In the Linux kernel, the following vulnerability has been resolved: misc: ocxl: fix possible name leak in ocxlfileregisterafu If deviceregister returns error in ocxlfileregisterafu, the name allocated by devsetname need be freed. As comment of deviceregister says, it should use putdevice to give ...
UBUNTU-CVE-2022-50669
In the Linux kernel, the following vulnerability has been resolved: misc: ocxl: fix possible name leak in ocxlfileregisterafu If deviceregister returns error in ocxlfileregisterafu, the name allocated by devsetname need be freed. As comment of deviceregister says, it should use putdevice to give ...
CVE-2022-50669
In CVE-2022-50669, the Linux kernel’s misc: ocxl subsystem contains a name-leak risk in ocxl_file_register_afu() when device_register() errors. The root cause is that the name allocated via dev_set_name() isn’t freed on error, delaying cleanup until kobject_cleanup() and info_release(). The fix a...
CVE-2025-40188 pwm: berlin: Fix wrong register in suspend/resume
In the Linux kernel, the following vulnerability has been resolved: pwm: berlin: Fix wrong register in suspend/resume The 'enable' register should be BERLINPWMEN rather than BERLINPWMENABLE, otherwise, the driver accesses wrong address, there will be cpu exception then kernel panic during...
Linux Distros Unpatched Vulnerability : CVE-2022-50547
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - media: solo6x10: fix possible memory leak in solosysfsinit If deviceregister returns error in solosysfsinit, the name allocated by devsetname need be freed. As...
SUSE CVE-2022-50547
In the Linux kernel, the following vulnerability has been resolved: media: solo6x10: fix possible memory leak in solosysfsinit If deviceregister returns error in solosysfsinit, the name allocated by devsetname need be freed. As comment of deviceregister says, it should use putdevice to give up th...
EUVD-2025-32810
In the Linux kernel, the following vulnerability has been resolved: media: solo6x10: fix possible memory leak in solosysfsinit If deviceregister returns error in solosysfsinit, the name allocated by devsetname need be freed. As comment of deviceregister says, it should use putdevice to give up th...
CVE-2022-50538 vme: Fix error not catched in fake_init()
In the Linux kernel, the following vulnerability has been resolved: vme: Fix error not catched in fakeinit In fakeinit, rootdeviceregister is possible to fail but it's ignored, which can cause unregistering vmeroot fail when exit. general protection fault, probably for non-canonical address...
PT-2025-41052
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A memory leak exists in the solo sysfs init function within the solo6x10 driver. If device register returns an error during initialization, memory allocated by dev set name is not freed...
EUVD-2022-55613
Malicious code in bioql PyPI...
SUSE CVE-2022-50349
In the Linux kernel, the following vulnerability has been resolved: misc: tifm: fix possible memory leak in tifm7xx1switchmedia If deviceregister returns error in tifm7xx1switchmedia, name of kobject which is allocated in devsetname called in deviceadd is leaked. Never directly free @dev after...
DEBIAN-CVE-2022-50349
In the Linux kernel, the following vulnerability has been resolved: misc: tifm: fix possible memory leak in tifm7xx1switchmedia If deviceregister returns error in tifm7xx1switchmedia, name of kobject which is allocated in devsetname called in deviceadd is leaked. Never directly free @dev after...
CVE-2022-50349 misc: tifm: fix possible memory leak in tifm_7xx1_switch_media()
In the Linux kernel, the following vulnerability has been resolved: misc: tifm: fix possible memory leak in tifm7xx1switchmedia If deviceregister returns error in tifm7xx1switchmedia, name of kobject which is allocated in devsetname called in deviceadd is leaked. Never directly free @dev after...
CVE-2022-50349 misc: tifm: fix possible memory leak in tifm_7xx1_switch_media()
In the Linux kernel, the following vulnerability has been resolved: misc: tifm: fix possible memory leak in tifm7xx1switchmedia If deviceregister returns error in tifm7xx1switchmedia, name of kobject which is allocated in devsetname called in deviceadd is leaked. Never directly free @dev after...
CVE-2025-9005
The vulnerability CVE-2025-9005 affects mtons mblog up to version 3.5.0, where an unknown function in the /register endpoint can trigger information exposure via an error message. It can be exploited remotely; attack complexity is high and exploitation is not trivial. Public disclosure exists, wi...
Linux Distros Unpatched Vulnerability : CVE-2025-22026
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - nfsd: don't ignore the return code of svcprocregister Currently, nfsdprocstatinit ignores the return value of svcprocregister. If the procfile creation fails,...
Linux Distros Unpatched Vulnerability : CVE-2021-47287
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - In the Linux kernel, the following vulnerability has been resolved: driver core: auxiliary bus: Fix memory leak when driverregister fail If driverregister retur...
UBUNTU-CVE-2025-37877
In the Linux kernel, the following vulnerability has been resolved: iommu: Clear iommu-dma ops on cleanup If iommudeviceregister encounters an error, it can end up tearing down already-configured groups and default domains, however this currently still leaves devices hooked up to iommu-dma and ev...
SUSE CVE-2022-49836
In the Linux kernel, the following vulnerability has been resolved: siox: fix possible memory leak in sioxdeviceadd If deviceregister returns error in sioxdeviceadd, the name allocated by devsetname need be freed. As comment of deviceregister says, it should use putdevice to give up the reference...
DEBIAN-CVE-2022-49836
In the Linux kernel, the following vulnerability has been resolved: siox: fix possible memory leak in sioxdeviceadd If deviceregister returns error in sioxdeviceadd, the name allocated by devsetname need be freed. As comment of deviceregister says, it should use putdevice to give up the reference...