Menu

Star on GitHub · 3.2k

CVE-2022-50763

In the Linux kernel, the following vulnerability has been resolved: crypto: marvell/octeontx - prevent integer overflows The "code_length" value comes from the firmware file.

Published Dec 24, 2025EPSS 0.26%

Overview

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

Technical description

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

crypto: marvell/octeontx - prevent integer overflows

The "code_length" value comes from the firmware file. If your firmware

is untrusted realistically there is probably very little you can do to

protect yourself. Still we try to limit the damage as much as possible.

Also Smatch marks any data read from the filesystem as untrusted and

prints warnings if it not capped correctly.

The "code_length * 2" can overflow. The round_up(ucode_size, 16) +

sizeof() expression can overflow too. Prevent these overflows.

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

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

How severe is CVE-2022-50763?

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

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

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