Menu

Star on GitHub · 3.2k

CVE-2022-50876

In the Linux kernel, the following vulnerability has been resolved: usb: musb: Fix musb_gadget.c rxstate overflow bug The usb function device call musb_gadget_queue() adds the passed request to m…

Published Dec 30, 2025EPSS 0.23%

Overview

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

Technical description

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

usb: musb: Fix musb_gadget.c rxstate overflow bug

The usb function device call musb_gadget_queue() adds the passed

request to musb_ep::req_list,If the (request->length > musb_ep->packet_sz)

and (is_buffer_mapped(req) return false),the rxstate() will copy all data

in fifo to request->buf which may cause request->buf out of bounds.

Fix it by add the length check :

fifocnt = min_t(unsigned, request->length - request->actual, fifocnt);

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

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

How severe is CVE-2022-50876?

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

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

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