All reports
Unknown

UBUNTU-CVE-2022-50734

Affected versions

Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<5.15.0-1030.34~20.04.1
Fixed version
5.15.0-1030.34~20.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<5.15.0-1033.40~20.04.1
Fixed version
5.15.0-1033.40~20.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<5.15.0-1029.36~20.04.1
Fixed version
5.15.0-1029.36~20.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<5.15.0-60.66~20.04.1
Fixed version
5.15.0-60.66~20.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<5.15.0-1025.30~20.04.1
Fixed version
5.15.0-1025.30~20.04.1
Affected versions
<5.15.0-60.66~20.04.1
Fixed version
5.15.0-60.66~20.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<5.15.0-1029.35~20.04.1
Fixed version
5.15.0-1029.35~20.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<5.15.0-1029.33~20.04.1
Fixed version
5.15.0-1029.33~20.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<5.15.0-1030.34
Fixed version
5.15.0-1030.34
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<5.15.0-1033.40.1
Fixed version
5.15.0-1033.40.1
Affected versions
<5.15.0-1033.40
Fixed version
5.15.0-1033.40
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<5.15.0-1029.36
Fixed version
5.15.0-1029.36
Affected versions
<5.15.0-1027.32
Fixed version
5.15.0-1027.32
Affected versions
<5.15.0-1015.19
Fixed version
5.15.0-1015.19
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<5.15.0-1025.28
Fixed version
5.15.0-1025.28
Affected versions
*
Fixed version
Not reported
Affected versions
<5.15.0-1025.30
Fixed version
5.15.0-1025.30
Affected versions
<5.15.0-1028.33
Fixed version
5.15.0-1028.33
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<5.15.0-60.66
Fixed version
5.15.0-60.66
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<5.15.0-1017.17
Fixed version
5.15.0-1017.17
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<5.15.0-1029.35
Fixed version
5.15.0-1029.35
Affected versions
<5.15.0-1024.26
Fixed version
5.15.0-1024.26
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<5.15.0-60.66
Fixed version
5.15.0-60.66
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<5.15.0-1014.16
Fixed version
5.15.0-1014.16

Description

In the Linux kernel, the following vulnerability has been resolved: nvmem: core: Fix memleak in nvmem_register() dev_set_name will alloc memory for nvmem->dev.kobj.name in nvmem_register, when nvmem_validate_keepouts failed, nvmem's memory will be freed and return, but nobody will free memory for nvmem->dev.kobj.name, there will be memleak, so moving nvmem_validate_keepouts() after device_register() and let the device core deal with cleaning name in error cases.

Links