{"uuid": "6eee020a-6db4-4210-ac2a-c457ccd332bb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21704", "type": "seen", "source": "https://t.me/cvedetector/18711", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21704 - Linux Kernel usb-cdc-acm Memory Corruption Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21704 \nPublished : Feb. 22, 2025, 10:15 a.m. | 1\u00a0hour ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nusb: cdc-acm: Check control transfer buffer size before access  \n  \nIf the first fragment is shorter than struct usb_cdc_notification, we can't  \ncalculate an expected_size. Log an error and discard the notification  \ninstead of reading lengths from memory outside the received data, which can  \nlead to memory corruption when the expected_size decreases between  \nfragments, causing `expected_size - acm->nb_index` to wrap.  \n  \nThis issue has been present since the beginning of git history; however,  \nit only leads to memory corruption since commit ea2583529cd1  \n(\"cdc-acm: reassemble fragmented notifications\").  \n  \nA mitigating factor is that acm_ctrl_irq() can only execute after userspace  \nhas opened /dev/ttyACM*; but if ModemManager is running, ModemManager will  \ndo that automatically depending on the USB device's vendor/product IDs and  \nits other interfaces. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"22 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-22T12:29:06.000000Z"}