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-74457can: peak_usb: add bounds check for USB channel index

Description

In the Linux kernel, the following vulnerability has been resolved: can: peak_usb: add bounds check for USB channel index The channel control index ctrl_idx is derived from rx->len which comes directly from a device USB payload. The mask 0x0f allows values 0-15, but the array size of usb_if->dev[] is only 2. Values 2-15 cause heap out-of-bounds read, eventually causing kernel panic in the IRQ context. Add bounds checking for ctrl_idx before the array access in both pcan_usb_pro_handle_canmsg() and pcan_usb_pro_handle_error().

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 3 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (17 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: Not scored.

Affected products

  • Linux · Linux

    • affected d8a199355f8f8a0797c00d98788d7282c9ea38bd – < 18b1a868a2cda66fb438007ba47ce5f2484db381
    • affected d8a199355f8f8a0797c00d98788d7282c9ea38bd – < 0c9268457bd6e4058fe55b4db01b16661c2eacf5
    • affected d8a199355f8f8a0797c00d98788d7282c9ea38bd – < 94fb6fe83ce152532b11b36730b30f3dc0c94217
    • affected d8a199355f8f8a0797c00d98788d7282c9ea38bd – < 825c903ca3c98cd0cf0e3de8ab8f2604a5339b3f
    • affected d8a199355f8f8a0797c00d98788d7282c9ea38bd – < f97b7e5e1cdaae15cd95b3a360028c7929664969
    • affected d8a199355f8f8a0797c00d98788d7282c9ea38bd – < 1acab790b7cecd4e144d1d18bdfe549e282f6b0b
    • affected d8a199355f8f8a0797c00d98788d7282c9ea38bd – < 0149fdb50a30944827acf9600a2cc44de0325a7f
    • affected d8a199355f8f8a0797c00d98788d7282c9ea38bd – < 39132f166ca8ce00ae60d8a9068e06a60943cc4b
  • Linux · Linux

    • affected 3.4
    • unaffected < 3.4
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.151 – ≤ 6.6.*
    • unaffected 6.12.103 – ≤ 6.12.*
    • unaffected 6.18.44 – ≤ 6.18.*
    • unaffected 7.1.8 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .