1. Home
  2. Vulnerabilities
  3. CVE-2025-68308
0.0
NA
CVE-2025-68308
can: kvaser_usb: leaf: Fix potential infinite loop in command parsers
Description

In the Linux kernel, the following vulnerability has been resolved: can: kvaser_usb: leaf: Fix potential infinite loop in command parsers The `kvaser_usb_leaf_wait_cmd()` and `kvaser_usb_leaf_read_bulk_callback` functions contain logic to zero-length commands. These commands are used to align data to the USB endpoint's wMaxPacketSize boundary. The driver attempts to skip these placeholders by aligning the buffer position `pos` to the next packet boundary using `round_up()` function. However, if zero-length command is found exactly on a packet boundary (i.e., `pos` is a multiple of wMaxPacketSize, including 0), `round_up` function will return the unchanged value of `pos`. This prevents `pos` to be increased, causing an infinite loop in the parsing logic. This patch fixes this in the function by using `pos + 1` instead. This ensures that even if `pos` is on a boundary, the calculation is based on `pos + 1`, forcing `round_up()` to always return the next aligned boundary.

INFO

Published Date :

Dec. 16, 2025, 4:16 p.m.

Last Modified :

Dec. 16, 2025, 4:16 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2025-68308 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
: Total Affected Vendor : 1 | Products : 1
Solution
Update the Linux kernel to fix an infinite loop vulnerability in the Kvaser USB leaf driver.
  • Apply the provided kernel patch.
  • Recompile the kernel with the patch.
  • Install the updated kernel.
  • Reboot the system.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2025-68308.

URL Resource
https://git.kernel.org/stable/c/028e89c7e8b4346302e88df01cc50e0a1f05791a
https://git.kernel.org/stable/c/0897cea266e39166a36111059ba147192b36592f
https://git.kernel.org/stable/c/0c73772cd2b8cc108d5f5334de89ad648d89b9ec
https://git.kernel.org/stable/c/58343e0a4d43699f0e2f5b169384bbe4c0217add
https://git.kernel.org/stable/c/69c7825df64e24dc15d31631a1fc9145324b1345
https://git.kernel.org/stable/c/bd8135a560cf6e64f0b98ed4daadf126a38f7f48
https://git.kernel.org/stable/c/e9dd83a75a7274edef21682c823bf0b66d7b6b7f
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2025-68308 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2025-68308 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2025-68308 vulnerability anywhere in the article.

Results are limited to the first 20 news articles due to potential performance issues.

The following table lists the changes that have been made to the CVE-2025-68308 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Dec. 16, 2025

    Action Type Old Value New Value
    Added Description In the Linux kernel, the following vulnerability has been resolved: can: kvaser_usb: leaf: Fix potential infinite loop in command parsers The `kvaser_usb_leaf_wait_cmd()` and `kvaser_usb_leaf_read_bulk_callback` functions contain logic to zero-length commands. These commands are used to align data to the USB endpoint's wMaxPacketSize boundary. The driver attempts to skip these placeholders by aligning the buffer position `pos` to the next packet boundary using `round_up()` function. However, if zero-length command is found exactly on a packet boundary (i.e., `pos` is a multiple of wMaxPacketSize, including 0), `round_up` function will return the unchanged value of `pos`. This prevents `pos` to be increased, causing an infinite loop in the parsing logic. This patch fixes this in the function by using `pos + 1` instead. This ensures that even if `pos` is on a boundary, the calculation is based on `pos + 1`, forcing `round_up()` to always return the next aligned boundary.
    Added Reference https://git.kernel.org/stable/c/028e89c7e8b4346302e88df01cc50e0a1f05791a
    Added Reference https://git.kernel.org/stable/c/0897cea266e39166a36111059ba147192b36592f
    Added Reference https://git.kernel.org/stable/c/0c73772cd2b8cc108d5f5334de89ad648d89b9ec
    Added Reference https://git.kernel.org/stable/c/58343e0a4d43699f0e2f5b169384bbe4c0217add
    Added Reference https://git.kernel.org/stable/c/69c7825df64e24dc15d31631a1fc9145324b1345
    Added Reference https://git.kernel.org/stable/c/bd8135a560cf6e64f0b98ed4daadf126a38f7f48
    Added Reference https://git.kernel.org/stable/c/e9dd83a75a7274edef21682c823bf0b66d7b6b7f
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
No CVSS metrics available for this vulnerability.