Answer in brief
CVE-2026-74456 records a Unknown severity vulnerability in can: peak_usb: peak_usb_start(): fix double free of transfer buffer on URB submit error. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d <525640b93d3e5f82f4ebea4730f4e0cf799522ba || >=bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d <4bb3325075138dd5346b71589a959878b564dc0b || >=bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d <92d0de80ca2223b9c7da78020155b6cb27824cc0 || >=bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d <dfb17bf04a764462000f11258a7c06aa92d1f261 || >=bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d <9b3d5a6d952c38bbcf07f903cbeadefdb56b9bc9 | 525640b93d3e5f82f4ebea4730f4e0cf799522ba, 4bb3325075138dd5346b71589a959878b564dc0b, 92d0de80ca2223b9c7da78020155b6cb27824cc0, dfb17bf04a764462000f11258a7c06aa92d1f261, 9b3d5a6d952c38bbcf07f903cbeadefdb56b9bc9 |
| Linux/Linuxgeneric | 3.4 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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").
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-74456 records a Unknown severity vulnerability in can: peak_usb: peak_usb_start(): fix double free of transfer buffer on URB submit error. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d <525640b93d3e5f82f4ebea4730f4e0cf799522ba || >=bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d <4bb3325075138dd5346b71589a959878b564dc0b || >=bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d <92d0de80ca2223b9c7da78020155b6cb27824cc0 || >=bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d <dfb17bf04a764462000f11258a7c06aa92d1f261 || >=bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d <9b3d5a6d952c38bbcf07f903cbeadefdb56b9bc9 | 525640b93d3e5f82f4ebea4730f4e0cf799522ba, 4bb3325075138dd5346b71589a959878b564dc0b, 92d0de80ca2223b9c7da78020155b6cb27824cc0, dfb17bf04a764462000f11258a7c06aa92d1f261, 9b3d5a6d952c38bbcf07f903cbeadefdb56b9bc9 |
| Linux/Linuxgeneric | 3.4 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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").
Quoted source text, attributed separately from HOL analysis.