https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 04:32:32 +0000 https://vulnerability.circl.lu/vuln/cve-2024-53213 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: usb: lan78xx: Fix double free issue with interrupt buffer allocation</p> <p>In lan78xx_probe(), the buffer `buf` was being freed twice: once implicitly through `usb_free_urb(dev-&gt;urb_intr)` with the `URB_FREE_BUFFER` flag and again explicitly by `kfree(buf)`. This caused a double free issue.</p> <p>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.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: usb: lan78xx: Fix double free issue with interrupt buffer allocation</p> <p>In lan78xx_probe(), the buffer `buf` was being freed twice: once implicitly through `usb_free_urb(dev-&gt;urb_intr)` with the `URB_FREE_BUFFER` flag and again explicitly by `kfree(buf)`. This caused a double free issue.</p> <p>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.</p> https://vulnerability.circl.lu/vuln/cve-2024-53213