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...

SUSE 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...

EUVD-2022-55841

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...

CVE-2022-50857 rapidio: rio: fix possible name leak in rio_register_mport()

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...

CVE-2022-50857

The CVE-2022-50857 entry concerns the Linux kernel code path for rapidio rio: rio_register_mport. The issue arises when device_register() fails after an mport name has been allocated with dev_set_name(); the allocated name must be released, and the reference should be dropped with put_device() so...