Menu

Star on GitHub · 3.2k

CVE-2022-50642

In the Linux kernel, the following vulnerability has been resolved: platform/chrome: cros_ec_typec: zero out stale pointers `cros_typec_get_switch_handles` allocates four pointers when obtaining…

Published Dec 9, 2025EPSS 0.20%

Overview

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

Technical description

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

platform/chrome: cros_ec_typec: zero out stale pointers

`cros_typec_get_switch_handles` allocates four pointers when obtaining

type-c switch handles. These pointers are all freed if failing to obtain

any of them; therefore, pointers in `port` become stale. The stale

pointers eventually cause use-after-free or double free in later code

paths. Zeroing out all pointer fields after freeing to eliminate these

stale pointers.

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

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

How severe is CVE-2022-50642?

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

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

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