Menu

Star on GitHub · 3.2k

CVE-2022-50557

In the Linux kernel, the following vulnerability has been resolved: pinctrl: thunderbay: fix possible memory leak in thunderbay_build_functions() The thunderbay_add_functions() will free memory o…

Published Oct 22, 2025EPSS 0.21%

Overview

CVE-2022-50557 is a known-severity vulnerability. It was published on October 22, 2025.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

pinctrl: thunderbay: fix possible memory leak in thunderbay_build_functions()

The thunderbay_add_functions() will free memory of thunderbay_funcs

when everything is ok, but thunderbay_funcs will not be freed when

thunderbay_add_functions() fails, then there will be a memory leak,

so we need to add kfree() when thunderbay_add_functions() fails to

fix it.

In addition, doing some cleaner works, moving kfree(funcs) from

thunderbay_add_functions() to thunderbay_build_functions().

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-50557?

CVE-2022-50557 is a known-severity vulnerability. It was published on October 22, 2025.

How severe is CVE-2022-50557?

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-50557?

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-50557?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-50557 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.