BaseFortify

Publication date: 2025-10-07

Last updated on: 2026-02-26

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: media: solo6x10: fix possible memory leak in solo_sysfs_init() If device_register() returns error in solo_sysfs_init(), the name allocated by dev_set_name() need be freed. As comment of device_register() says, it should use put_device() to give up the reference in the error path. So fix this by calling put_device(), then the name can be freed in kobject_cleanup().

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2025-10-07

Last Modified

2026-02-26

Generated

2026-07-06

AI Q&A

2025-10-07

EPSS Evaluated

2026-07-05

NVD

CVE-2022-50547

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	From 4.10 (inc) to 4.14.303 (inc)
linux	kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-401	The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

Attack-Flow Graph

Executive Summary

This vulnerability is a possible memory leak in the Linux kernel's solo6x10 media driver. Specifically, if the device_register() function returns an error during the solo_sysfs_init() initialization, the name allocated by dev_set_name() is not properly freed. The fix involves calling put_device() to release the device reference, allowing the allocated name to be freed correctly during kobject_cleanup().

Impact Analysis

This vulnerability can lead to a memory leak in the Linux kernel when the solo6x10 media driver fails to register a device properly. Over time, this could cause increased memory usage and potentially degrade system performance or stability.

Hi! I’m here to help you understand CVE-2022-50547. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70