{"uuid": "8d021951-e63f-4ac6-b572-f22810190a76", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-58079", "type": "seen", "source": "https://t.me/cvedetector/19727", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-58079 - Linux UVC Driver GPIO Unbind Crash Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-58079 \nPublished : March 6, 2025, 5:15 p.m. | 1\u00a0hour ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nmedia: uvcvideo: Fix crash during unbind if gpio unit is in use  \n  \nWe used the wrong device for the device managed functions. We used the  \nusb device, when we should be using the interface device.  \n  \nIf we unbind the driver from the usb interface, the cleanup functions  \nare never called. In our case, the IRQ is never disabled.  \n  \nIf an IRQ is triggered, it will try to access memory sections that are  \nalready free, causing an OOPS.  \n  \nWe cannot use the function devm_request_threaded_irq here. The devm_*  \nclean functions may be called after the main structure is released by  \nuvc_delete.  \n  \nLuckily this bug has small impact, as it is only affected by devices  \nwith gpio units and the user has to unbind the device, a disconnect will  \nnot trigger this error. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"06 Mar 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-03-06T19:41:48.000000Z"}