{"vulnerability": "CVE-2025-21704", "sightings": [{"uuid": "4803b684-0949-40e1-adf5-7f9bfb53315f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21704", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/5019", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21704\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: 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.\n\ud83d\udccf Published: 2025-02-22T09:43:37.377Z\n\ud83d\udccf Modified: 2025-02-22T09:43:37.377Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/7828e9363ac4d23b02419bf2a45b9f1d9fb35646\n2. https://git.kernel.org/stable/c/6abb510251e75f875797d8983a830e6731fa281c\n3. https://git.kernel.org/stable/c/f64079bef6a8a7823358c3f352ea29a617844636\n4. https://git.kernel.org/stable/c/383d516a0ebc8641372b521c8cb717f0f1834831\n5. https://git.kernel.org/stable/c/e563b01208f4d1f609bcab13333b6c0e24ce6a01", "creation_timestamp": "2025-02-22T10:26:05.000000Z"}, {"uuid": "d121c616-b550-4772-907d-d6acf875ad8a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21704", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/114047226500494320", "content": "", "creation_timestamp": "2025-02-22T11:09:34.329149Z"}, {"uuid": "c9e0f2f7-de5e-438a-9b79-6237a57a21e8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21704", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3liraysjppu23", "content": "", "creation_timestamp": "2025-02-22T11:52:24.787138Z"}, {"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"}]}