CVE-2025-68343
Unknown Unknown - Not Provided
Integer Underflow in Linux Kernel gs_usb Driver Causes Memory Access Error

Publication date: 2025-12-23

Last updated on: 2025-12-23

Assigner: kernel.org

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-23
Last Modified
2025-12-23
Generated
2026-05-07
AI Q&A
2025-12-24
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?

Apply the patch or update to the fixed version of the Linux kernel that includes the correction in the gs_usb driver, specifically the fix in gs_usb_receive_bulk_callback() to properly check actual_length before accessing the header. Avoid using vulnerable kernel versions until patched.


Can you explain this vulnerability to me?

This vulnerability in the Linux kernel's gs_usb driver involves improper checking of the actual_length before accessing the header in the gs_usb_receive_bulk_callback() function. The driver expects to receive a struct gs_host_frame, but it did not verify that the received data was at least the size of the header before accessing its members. This could lead to dereferencing invalid pointers if the received data is too short. The fix involves using struct_group to describe the header and checking the length before access, and correctly resubmitting the URB by using a pointer that is always defined.


How can this vulnerability impact me? :

This vulnerability could lead to kernel crashes or undefined behavior due to dereferencing invalid pointers when processing USB data in the gs_usb driver. This may result in system instability or potential denial of service if exploited.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart