{"vulnerability": "CVE-2025-21776", "sightings": [{"uuid": "b4ba68d5-a768-4187-a073-1a9b29cbb9a1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21776", "type": "seen", "source": "https://gist.github.com/Darkcrai86/0bb69cc9f5226c3ef22886c4a9ccbd31", "content": "", "creation_timestamp": "2025-08-28T17:44:17.000000Z"}, {"uuid": "8409fb53-bbb6-46a9-b175-c2a71c3f896d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21776", "type": "published-proof-of-concept", "source": "https://t.me/cvedetector/19015", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21776 - \"Linux USB Hub: NULL Pointer Dereference Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-21776 \nPublished : Feb. 27, 2025, 3:15 a.m. | 1\u00a0hour, 54\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nUSB: hub: Ignore non-compliant devices with too many configs or interfaces  \n  \nRobert Morris created a test program which can cause  \nusb_hub_to_struct_hub() to dereference a NULL or inappropriate  \npointer:  \n  \nOops: general protection fault, probably for non-canonical address  \n0xcccccccccccccccc: 0000 [#1] SMP DEBUG_PAGEALLOC PTI  \nCPU: 7 UID: 0 PID: 117 Comm: kworker/7:1 Not tainted 6.13.0-rc3-00017-gf44d154d6e3d #14  \nHardware name: FreeBSD BHYVE/BHYVE, BIOS 14.0 10/17/2021  \nWorkqueue: usb_hub_wq hub_event  \nRIP: 0010:usb_hub_adjust_deviceremovable+0x78/0x110  \n...  \nCall Trace:  \n   \n ? die_addr+0x31/0x80  \n ? exc_general_protection+0x1b4/0x3c0  \n ? asm_exc_general_protection+0x26/0x30  \n ? usb_hub_adjust_deviceremovable+0x78/0x110  \n hub_probe+0x7c7/0xab0  \n usb_probe_interface+0x14b/0x350  \n really_probe+0xd0/0x2d0  \n ? __pfx___device_attach_driver+0x10/0x10  \n __driver_probe_device+0x6e/0x110  \n driver_probe_device+0x1a/0x90  \n __device_attach_driver+0x7e/0xc0  \n bus_for_each_drv+0x7f/0xd0  \n __device_attach+0xaa/0x1a0  \n bus_probe_device+0x8b/0xa0  \n device_add+0x62e/0x810  \n usb_set_configuration+0x65d/0x990  \n usb_generic_driver_probe+0x4b/0x70  \n usb_probe_device+0x36/0xd0  \n  \nThe cause of this error is that the device has two interfaces, and the  \nhub driver binds to interface 1 instead of interface 0, which is where  \nusb_hub_to_struct_hub() looks.  \n  \nWe can prevent the problem from occurring by refusing to accept hub  \ndevices that violate the USB spec by having more than one  \nconfiguration or interface. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-27T06:11:41.000000Z"}]}