can: peak_usb: peak_usb_start(): fix double free of transfer buffer on URB submit error
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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").
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d · fixed in 914c3b8fa175acf8476ad31cf04e308638e3578e; From bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d · fixed in 5f2fa5840c34d3a558c57855781be75e03bef752; From bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d · fixed in b9088d581fff971a7eb1628f8dcc30df6cfef4dc; From bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d · fixed in 525640b93d3e5f82f4ebea4730f4e0cf799522ba; From bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d · fixed in 4bb3325075138dd5346b71589a959878b564dc0b; From bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d · fixed in 92d0de80ca2223b9c7da78020155b6cb27824cc0; From bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d · fixed in dfb17bf04a764462000f11258a7c06aa92d1f261; From bb4785551f64e18b2c8bb15a3bd2b22f5ebf624d · fixed in 9b3d5a6d952c38bbcf07f903cbeadefdb56b9bc9
- Linux Linux
3.4
- KernelLinux
From 3.4.0 · fixed in 5.10.265; From 5.11.0 · fixed in 5.15.216; From 5.16.0 · fixed in 6.1.183; From 6.2.0 · fixed in 6.6.151; From 6.7.0 · fixed in 6.12.103; From 6.13.0 · fixed in 6.18.44; From 6.19.0 · fixed in 7.1.8
References 8
git.kernel.org
- stable/c/914c3b8fa175acf8476ad31cf04e308638e3578e
- stable/c/5f2fa5840c34d3a558c57855781be75e03bef752
- stable/c/b9088d581fff971a7eb1628f8dcc30df6cfef4dc
- stable/c/525640b93d3e5f82f4ebea4730f4e0cf799522ba
- stable/c/4bb3325075138dd5346b71589a959878b564dc0b
- stable/c/92d0de80ca2223b9c7da78020155b6cb27824cc0
- stable/c/dfb17bf04a764462000f11258a7c06aa92d1f261
- stable/c/9b3d5a6d952c38bbcf07f903cbeadefdb56b9bc9