Menu

Star on GitHub · 3.2k

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 nv…

Published Dec 24, 2025EPSS 0.24%

Overview

CVE-2022-50734 is a known-severity vulnerability. It was published on December 24, 2025.

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

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2022-50734?

CVE-2022-50734 is a known-severity vulnerability. It was published on December 24, 2025.

How severe is CVE-2022-50734?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2022-50734?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-50734?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-50734 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.