CVE-2026-74456

can: peak_usb: peak_usb_start(): fix double free of transfer buffer on URB submit error

HIGH
7.8
CVSS Score
Published: August 15, 2026 at 12:26 PM UTC
Updated: October 16, 2026 at 08:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: can: peak_usb: peak_usb_start(): fix double free of transfer buffer on URB submit error In peak_usb_start(), each RX URB transfer buffer is allocated with kmalloc() and the URB is flagged URB_FREE_BUFFER so that the final usb_free_urb() also frees the transfer buffer. If usb_submit_urb() fails, the error path frees the buffer explicitly with kfree(buf) and then calls usb_free_urb(urb). Because URB_FREE_BUFFER is set, usb_free_urb() -> urb_destroy() frees the same buffer a second time, a double free of the transfer buffer. BUG: KASAN: double-free in usb_free_urb.part.0+0x91/0xb0 Free of addr ffff8881069ccb80 by task trigger.sh/285 Call Trace: kfree+0x113/0x3c0 usb_free_urb.part.0+0x91/0xb0 Drop the redundant kfree(buf); usb_free_urb() already releases the transfer buffer. This mirrors commit 03819abbeb11 ("net: usb: lan78xx: Fix double free issue with interrupt buffer allocation").

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.4bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d
Vendor states this is fixed in 4bb3325075138dd5346b71589a959878b564dc0b (fixed)
Vendor states this is fixed in 525640b93d3e5f82f4ebea4730f4e0cf799522ba (fixed)
Vendor states this is fixed in 5f2fa5840c34d3a558c57855781be75e03bef752 (fixed)
Vendor states this is fixed in 914c3b8fa175acf8476ad31cf04e308638e3578e (fixed)
Vendor states this is fixed in 92d0de80ca2223b9c7da78020155b6cb27824cc0 (fixed)
Vendor states this is fixed in 9b3d5a6d952c38bbcf07f903cbeadefdb56b9bc9 (fixed)
Vendor states this is fixed in b9088d581fff971a7eb1628f8dcc30df6cfef4dc (fixed)
Vendor states this is fixed in dfb17bf04a764462000f11258a7c06aa92d1f261 (fixed)
Vendor states this is fixed in 3.4 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card