CVE-2026-74456

CVE CVE-2026-74456EUVD EUVD-2026-59649Published 2026-08-15T12:26:58.000ZLast changed 2026-08-19T16:36:51.000ZCVSS 7.8

What the advisory describes

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").

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d <dfb17bf04a764462000f11258a7c06aa92d1f261; bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d <4bb3325075138dd5346b71589a959878b564dc0b; patch: 6.18.44; bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d <525640b93d3e5f82f4ebea4730f4e0cf799522ba; bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d <5f2fa5840c34d3a558c57855781be75e03bef752; patch: 5.10.265; patch: 7.1.8; bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d <9b3d5a6d952c38bbcf07f903cbeadefdb56b9bc9; patch: 7.2; patch: 0; bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d <92d0de80ca2223b9c7da78020155b6cb27824cc0; patch: 6.1.183; patch: 6.6.151; patch: 5.15.216; bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d <b9088d581fff971a7eb1628f8dcc30df6cfef4dc; patch: 6.12.103; bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d <914c3b8fa175acf8476ad31cf04e308638e3578e; 3.4

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.