Strix
26.1K

CVE-2022-50734

UnknownEPSS 0.20%

Last modified

CVE-2022-50734 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.20% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.20%

10.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= de0534df93474f268486c486ea7e01b44a478026, < 9391cc3a787a58aa224a6440d7f244d780ba2896; >= de0534df93474f268486c486ea7e01b44a478026, < 2bd2774df0ce37920b23819a860a66fdbdd90823; >= de0534df93474f268486c486ea7e01b44a478026, < b6054b9b239a493672f853b034570cca93ba7a88; >= de0534df93474f268486c486ea7e01b44a478026, < bd1244561fa2a4531ded40dbf09c9599084f8b29; c1d44b93ca9f3ebc26b0de0a7f4b7156702762b6; 63c2b13ba0428b8f477e4adb1d40a50eb4493c09; >= 5.13.19, < 5.14; >= 5.14.6, < 5.15
LinuxLinux5.15

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2022-50734?
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.
How severe is CVE-2022-50734?
Severity scoring for CVE-2022-50734 is pending analysis. The EPSS model estimates a 0.20% probability of exploitation in the next 30 days.
How do I fix CVE-2022-50734?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2022

View all 2022CVEs →

Are you affected by CVE-2022-50734?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST