https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 07:58:46 +0000 https://vulnerability.circl.lu/vuln/cve-2026-68344 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>usb: atm: ueagle-atm: reject descriptors that confuse probe and disconnect</p> <p>uea_probe() distinguishes a pre-firmware device from a post-firmware one using the USB id (UEA_IS_PREFIRM()), and stores a different object as the interface data in each case: a &#39;struct completion&#39; for a pre-firmware device (to be waited on in .disconnect()), or a &#39;struct usbatm_data&#39; for a post-firmware one.</p> <p>uea_disconnect() instead tells the two apart by the number of interfaces of the active configuration (a pre-firmware device exposes a single interface, ADI930 has 2 and eagle has 3), and casts the interface data accordingly.</p> <p>Because the two handlers use different criteria, a crafted device that advertises a pre-firmware id together with a multi-interface descriptor (or a post-firmware id with a single interface) makes them disagree: the small &#39;struct completion&#39; stored by uea_probe() is then passed to usbatm_usb_disconnect(), which casts it to &#39;struct usbatm_data&#39; and takes instance-&gt;serialize, reading past the end of the allocation:</p> <p>BUG: KASAN: slab-out-of-bounds in __mutex_lock+0x152a/0x1b80 Read of size 8 at addr ffff8880470e2c60 by task kworker/1:2/982 ... __mutex_lock+0x152a/0x1b80 usbatm_usb_disconnect+0x70/0x820 uea_disconnect+0x133/0x2c0 usb_unbind_interface+0x1dd/0x9e0 ... which belongs to the cache kmalloc-96 of size 96 The buggy address is located 0 bytes to the right of allocated 96-byt…</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>usb: atm: ueagle-atm: reject descriptors that confuse probe and disconnect</p> <p>uea_probe() distinguishes a pre-firmware device from a post-firmware one using the USB id (UEA_IS_PREFIRM()), and stores a different object as the interface data in each case: a &#39;struct completion&#39; for a pre-firmware device (to be waited on in .disconnect()), or a &#39;struct usbatm_data&#39; for a post-firmware one.</p> <p>uea_disconnect() instead tells the two apart by the number of interfaces of the active configuration (a pre-firmware device exposes a single interface, ADI930 has 2 and eagle has 3), and casts the interface data accordingly.</p> <p>Because the two handlers use different criteria, a crafted device that advertises a pre-firmware id together with a multi-interface descriptor (or a post-firmware id with a single interface) makes them disagree: the small &#39;struct completion&#39; stored by uea_probe() is then passed to usbatm_usb_disconnect(), which casts it to &#39;struct usbatm_data&#39; and takes instance-&gt;serialize, reading past the end of the allocation:</p> <p>BUG: KASAN: slab-out-of-bounds in __mutex_lock+0x152a/0x1b80 Read of size 8 at addr ffff8880470e2c60 by task kworker/1:2/982 ... __mutex_lock+0x152a/0x1b80 usbatm_usb_disconnect+0x70/0x820 uea_disconnect+0x133/0x2c0 usb_unbind_interface+0x1dd/0x9e0 ... which belongs to the cache kmalloc-96 of size 96 The buggy address is located 0 bytes to the right of allocated 96-byt…</p> https://vulnerability.circl.lu/vuln/cve-2026-68344