Strix
26.1K

CVE-2025-68308

UnknownEPSS 0.16%

Last modified

CVE-2025-68308 is a vulnerability of currently unknown severity. 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`. EPSS estimates a 0.16% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.16%

5.7th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 7259124eac7d1b76b41c7a9cb2511a30556deebe, < 58343e0a4d43699f0e2f5b169384bbe4c0217add; >= 7259124eac7d1b76b41c7a9cb2511a30556deebe, < 69c7825df64e24dc15d31631a1fc9145324b1345; >= 7259124eac7d1b76b41c7a9cb2511a30556deebe, < 028e89c7e8b4346302e88df01cc50e0a1f05791a; >= 7259124eac7d1b76b41c7a9cb2511a30556deebe, < e9dd83a75a7274edef21682c823bf0b66d7b6b7f; >= 7259124eac7d1b76b41c7a9cb2511a30556deebe, < 0897cea266e39166a36111059ba147192b36592f; >= 7259124eac7d1b76b41c7a9cb2511a30556deebe, < bd8135a560cf6e64f0b98ed4daadf126a38f7f48; >= 7259124eac7d1b76b41c7a9cb2511a30556deebe, < 0c73772cd2b8cc108d5f5334de89ad648d89b9ec
LinuxLinux4.19

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2025-68308?
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.
How severe is CVE-2025-68308?
Severity scoring for CVE-2025-68308 is pending analysis. The EPSS model estimates a 0.16% probability of exploitation in the next 30 days.
How do I fix CVE-2025-68308?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2025

View all 2025CVEs →

Are you affected by CVE-2025-68308?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST