can: ucan: Fix infinite loop from zero-length messages
Summary
| CVE | CVE-2026-23298 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-03-25 11:16:25 UTC |
| Updated | 2026-04-18 09:16:17 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: can: ucan: Fix infinite loop from zero-length messages If a broken ucan device gets a message with the message length field set to 0, then the driver will loop for forever in ucan_read_bulk_callback(), hanging the system. If the length is 0, just skip the message and go on to the next one. This has been fixed in the kvaser_usb driver in the past in commit 0c73772cd2b8 ("can: kvaser_usb: leaf: Fix potential infinite loop in command parsers"), so there must be some broken devices out there like this somewhere. |
Risk And Classification
EPSS: 0.000320000 probability, percentile 0.090980000 (date 2026-04-18)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 9f2d3eae88d26c29d96e42983b755940d9169cd9 ca07d3c6eef14d34e6fdeefe55058db045be29dc git | Not specified |
| CNA | Linux | Linux | affected 9f2d3eae88d26c29d96e42983b755940d9169cd9 e7bb6e0606b5f233531aaaad9542d69fbb792115 git | Not specified |
| CNA | Linux | Linux | affected 9f2d3eae88d26c29d96e42983b755940d9169cd9 ab6f075492d37368b4c7b0df7f7fdc2b666887fc git | Not specified |
| CNA | Linux | Linux | affected 9f2d3eae88d26c29d96e42983b755940d9169cd9 13b646eec3ba1131180803f5aaf1fee23540ad8f git | Not specified |
| CNA | Linux | Linux | affected 9f2d3eae88d26c29d96e42983b755940d9169cd9 bd85f21a6219aeae4389d700c54f1799f4b814e0 git | Not specified |
| CNA | Linux | Linux | affected 9f2d3eae88d26c29d96e42983b755940d9169cd9 aa9e0a7fe5efc2f74327fd37d828e9a51d9ff588 git | Not specified |
| CNA | Linux | Linux | affected 9f2d3eae88d26c29d96e42983b755940d9169cd9 c7bc62be6c1a60bb21301692009590b1ffda91d9 git | Not specified |
| CNA | Linux | Linux | affected 9f2d3eae88d26c29d96e42983b755940d9169cd9 1e446fd0582ad8be9f6dafb115fc2e7245f9bea7 git | Not specified |
| CNA | Linux | Linux | affected 4.19 | Not specified |
| CNA | Linux | Linux | unaffected 4.19 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.10.253 5.10.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.203 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.167 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.130 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.77 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.17 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.19.7 6.19.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.0 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/ab6f075492d37368b4c7b0df7f7fdc2b666887fc | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/13b646eec3ba1131180803f5aaf1fee23540ad8f | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/e7bb6e0606b5f233531aaaad9542d69fbb792115 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/aa9e0a7fe5efc2f74327fd37d828e9a51d9ff588 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/ca07d3c6eef14d34e6fdeefe55058db045be29dc | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/1e446fd0582ad8be9f6dafb115fc2e7245f9bea7 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/bd85f21a6219aeae4389d700c54f1799f4b814e0 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/c7bc62be6c1a60bb21301692009590b1ffda91d9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.