1. Home
  2. Vulnerabilities
  3. CVE-2022-50547
0.0
NA
CVE-2022-50547
media: solo6x10: fix possible memory leak in solo_sysfs_init()
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().

INFO

Published Date :

Oct. 7, 2025, 4:15 p.m.

Last Modified :

Oct. 8, 2025, 7:38 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2022-50547 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
: Total Affected Vendor : 1 | Products : 1
Solution
Free allocated name if device registration fails to prevent memory leaks.
  • Call put_device() in the error path.
  • Ensure name is freed in kobject_cleanup().
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2022-50547.

URL Resource
https://git.kernel.org/stable/c/49060c0da57a381563e482e331dc9d4c3725b41b
https://git.kernel.org/stable/c/7b02c50d3978840781808e13bc13137fb81286b5
https://git.kernel.org/stable/c/7cf71bbe5d2ee12613f6e278888f5fc9c5c0cc2b
https://git.kernel.org/stable/c/7f5866dd96d95b74e439f6ee17b8abd8195179fb
https://git.kernel.org/stable/c/83d4b1ae98a47a739fa5241300b86eb1110d5d63
https://git.kernel.org/stable/c/9416861170ba0da8ddb0f4fd2d28334f0ed3b9c2
https://git.kernel.org/stable/c/963729538674be4cb8fa292529ecf32de0d6c6dd
https://git.kernel.org/stable/c/b61509093e1af69e336a094d439b8e1137cb40d8
https://git.kernel.org/stable/c/d6db105bcfbdbbbd484e788a0ddf8140a4a8c486
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2022-50547 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2022-50547 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2022-50547 vulnerability anywhere in the article.

Results are limited to the first 20 news articles due to potential performance issues.

The following table lists the changes that have been made to the CVE-2022-50547 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Oct. 07, 2025

    Action Type Old Value New Value
    Added 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().
    Added Reference https://git.kernel.org/stable/c/49060c0da57a381563e482e331dc9d4c3725b41b
    Added Reference https://git.kernel.org/stable/c/7b02c50d3978840781808e13bc13137fb81286b5
    Added Reference https://git.kernel.org/stable/c/7cf71bbe5d2ee12613f6e278888f5fc9c5c0cc2b
    Added Reference https://git.kernel.org/stable/c/7f5866dd96d95b74e439f6ee17b8abd8195179fb
    Added Reference https://git.kernel.org/stable/c/83d4b1ae98a47a739fa5241300b86eb1110d5d63
    Added Reference https://git.kernel.org/stable/c/9416861170ba0da8ddb0f4fd2d28334f0ed3b9c2
    Added Reference https://git.kernel.org/stable/c/963729538674be4cb8fa292529ecf32de0d6c6dd
    Added Reference https://git.kernel.org/stable/c/b61509093e1af69e336a094d439b8e1137cb40d8
    Added Reference https://git.kernel.org/stable/c/d6db105bcfbdbbbd484e788a0ddf8140a4a8c486
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
No CVSS metrics available for this vulnerability.