Menu

Star on GitHub · 3.2k

CVE-2025-68343

In the Linux kernel, the following vulnerability has been resolved: can: gs_usb: gs_usb_receive_bulk_callback(): check actual_length before accessing header The driver expects to receive a struct…

Published Dec 23, 2025EPSS 0.19%

Overview

CVE-2025-68343 is a known-severity vulnerability. It was published on December 23, 2025.

Technical description

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

can: gs_usb: gs_usb_receive_bulk_callback(): check actual_length before accessing header

The driver expects to receive a struct gs_host_frame in

gs_usb_receive_bulk_callback().

Use struct_group to describe the header of the struct gs_host_frame and

check that we have at least received the header before accessing any

members of it.

To resubmit the URB, do not dereference the pointer chain

"dev->parent->hf_size_rx" but use "parent->hf_size_rx" instead. Since

"urb->context" contains "parent", it is always defined, while "dev" is not

defined if the URB it too short.

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-2025-68343?

CVE-2025-68343 is a known-severity vulnerability. It was published on December 23, 2025.

How severe is CVE-2025-68343?

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-2025-68343?

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-2025-68343?

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