CVE-2025-68343
CVE-2025-68343 is a security vulnerability that is still awaiting full analysis and scoring. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.
Key facts
- EPSS exploit prediction: 0% (5th percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2025-204798
- Published:
- Last modified:
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.
Frequently asked questions
- What is 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 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.
- Is CVE-2025-68343 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (5th percentile), an estimate of the probability of exploitation in the next 30 days.
- How do I fix CVE-2025-68343?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- Does CVE-2025-68343 have an EU (EUVD) identifier?
- Yes. CVE-2025-68343 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-204798.
- When was CVE-2025-68343 published?
- CVE-2025-68343 was published on 2025-12-23 and last updated on 2026-06-17.
References
- https://git.kernel.org/stable/c/18cbce43363c9f84b90a92d57df341155eee0697
- https://git.kernel.org/stable/c/3433680b759646efcacc64fe36aa2e51ae34b8f0
- https://git.kernel.org/stable/c/616eee3e895b8ca0028163fcb1dce5e3e9dea322
- https://git.kernel.org/stable/c/6fe9f3279f7d2518439a7962c5870c6e9ecbadcf
- https://git.kernel.org/stable/c/f31693dc3a584c0ad3937e857b59dbc1a7ed2b87