Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-23298can: ucan: Fix infinite loop from zero-length messages

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.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 8 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-23298, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 9f2d3eae88d26c29d96e42983b755940d9169cd9 – < ca07d3c6eef14d34e6fdeefe55058db045be29dc
    • affected 9f2d3eae88d26c29d96e42983b755940d9169cd9 – < e7bb6e0606b5f233531aaaad9542d69fbb792115
    • affected 9f2d3eae88d26c29d96e42983b755940d9169cd9 – < ab6f075492d37368b4c7b0df7f7fdc2b666887fc
    • affected 9f2d3eae88d26c29d96e42983b755940d9169cd9 – < 13b646eec3ba1131180803f5aaf1fee23540ad8f
    • affected 9f2d3eae88d26c29d96e42983b755940d9169cd9 – < bd85f21a6219aeae4389d700c54f1799f4b814e0
    • affected 9f2d3eae88d26c29d96e42983b755940d9169cd9 – < aa9e0a7fe5efc2f74327fd37d828e9a51d9ff588
    • affected 9f2d3eae88d26c29d96e42983b755940d9169cd9 – < c7bc62be6c1a60bb21301692009590b1ffda91d9
    • affected 9f2d3eae88d26c29d96e42983b755940d9169cd9 – < 1e446fd0582ad8be9f6dafb115fc2e7245f9bea7
  • Linux · Linux

    • affected 4.19
    • unaffected < 4.19
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.167 – ≤ 6.1.*
    • unaffected 6.6.130 – ≤ 6.6.*
    • unaffected 6.12.77 – ≤ 6.12.*
    • unaffected 6.18.17 – ≤ 6.18.*
    • unaffected 6.19.7 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23298 badge
[![CVE-2026-23298](https://cveledger.app/badge/CVE-2026-23298.svg)](https://cveledger.app/cve/CVE-2026-23298)

Record last updated .