CVE-2026-74455: Linux kernel · can: peak_usb: validate uCAN receive record lengths
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d9c115948c3dd5fcc2d0245cec5eb76c098503c8 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 18:03 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in d9c115948c3dd5fcc2d0245cec5eb76c098503c8, bf9d787b7e1ef59be19b35abca08194772deb97e, 6067c878e38d02a3d5c43497347e143f85c9064a +5
Exploitation evidence
Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in multiple Linux kernel commits as listed in the established facts. Users and administrators should update to a Linux kernel version including these fixes to mitigate this vulnerability.
Description
A vulnerability in the Linux kernel's peak_usb CAN driver was addressed by validating uCAN receive record lengths. The function pcan_usb_fd_decode_buf() processes uCAN records in a USB receive buffer, and the fix requires each record to have a fixed header and verifies CAN payload bytes before copying them. This prevents potential issues from malformed or maliciously crafted CAN records.
References
- git.kernel.org/stable/c/276d989cd2dd88e2b7ab2c96fd10c86836b12781 (opens in a new tab)
- git.kernel.org/stable/c/bf9d787b7e1ef59be19b35abca08194772deb97e (opens in a new tab)
- git.kernel.org/stable/c/89c92a8052698dbbd3652a77c04d02bbd74a3275 (opens in a new tab)
- git.kernel.org/stable/c/6067c878e38d02a3d5c43497347e143f85c9064a (opens in a new tab)
- git.kernel.org/stable/c/2c8f08f3641a074da40acf05baa5a18ae2739260 (opens in a new tab)
- git.kernel.org/stable/c/2427ef427bdd78d862c7c76597bfd9eda88b81f1 (opens in a new tab)
- git.kernel.org/stable/c/d9c115948c3dd5fcc2d0245cec5eb76c098503c8 (opens in a new tab)
- git.kernel.org/stable/c/93fcab2c6968446316bbb49548848df604d6346f (opens in a new tab)