{"uuid": "21336160-f200-41cd-a73c-8c8fc314fb75", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-39484", "type": "seen", "source": "https://t.me/cvedetector/80", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-39484 - In the Linux kernel, the following vulnerability h\", \n  \"Content\": \"CVE ID : CVE-2024-39484 \nPublished : July 5, 2024, 7:15 a.m. | 17\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nmmc: davinci: Don't strip remove function when driver is builtin \n \nUsing __exit for the remove function results in the remove callback being \ndiscarded with CONFIG_MMC_DAVINCI=y. When such a device gets unbound (e.g. \nusing sysfs or hotplug), the driver is just removed without the cleanup \nbeing performed. This results in resource leaks. Fix it by compiling in the \nremove callback unconditionally. \n \nThis also fixes a W=1 modpost warning: \n \nWARNING: modpost: drivers/mmc/host/davinci_mmc: section mismatch in \nreference: davinci_mmcsd_driver+0x10 (section: .data) -> \ndavinci_mmcsd_remove (section: .exit.text) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-05T09:34:03.000000Z"}