net: usb: lan78xx: Fix double free issue with interrupt buffer allocation
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a6df95cae40bee555e01a37b4023ce8e97ffa249 · < 7ac9f3c981eeceee2ec4d30d850f4a6f50a1ec40| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: usb: lan78xx: Fix double free issue with interrupt buffer allocation
In lan78xx_probe(), the buffer `buf` was being freed twice: once implicitly through `usb_free_urb(dev->urb_intr)` with the `URB_FREE_BUFFER` flag and again explicitly by `kfree(buf)`. This caused a double free issue.
To resolve this, reordered `kmalloc()` and `usb_alloc_urb()` calls to simplify the initialization sequence and removed the redundant `kfree(buf)`. Now, `buf` is allocated after `usb_alloc_urb()`, ensuring it is correctly managed by `usb_fill_int_urb()` and freed by `usb_free_urb()` as intended.
From the CVE record · Linux
The Linux kernel’s lan78xx driver can free an interrupt buffer twice during device probing. The input does not establish what an attacker could do or specify network, local, authentication, or user-interaction conditions.
Teams running Linux kernels with the lan78xx USB network driver should check their versions; affected versions are not specified.