{"vulnerability": "cve-2024-5807", "sightings": [{"uuid": "30ef74f8-46c1-4693-abcc-0c90ab7884d7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-58076", "type": "seen", "source": "MISP/4937e86f-f5bd-4d09-8bda-88a7440077f3", "content": "", "creation_timestamp": "2025-08-18T13:31:23.000000Z"}, {"uuid": "5e666f2c-7ca5-4daa-aa65-92b161013431", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-58076", "type": "seen", "source": "MISP/4937e86f-f5bd-4d09-8bda-88a7440077f3", "content": "", "creation_timestamp": "2025-08-19T02:47:43.000000Z"}, {"uuid": "d45eb217-3b5b-4bf5-9ccb-e8cb11f9a1f9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-58076", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14792", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-58076\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nclk: qcom: gcc-sm6350: Add missing parent_map for two clocks\n\nIf a clk_rcg2 has a parent, it should also have parent_map defined,\notherwise we'll get a NULL pointer dereference when calling clk_set_rate\nlike the following:\n\n  [    3.388105] Call trace:\n  [    3.390664]  qcom_find_src_index+0x3c/0x70 (P)\n  [    3.395301]  qcom_find_src_index+0x1c/0x70 (L)\n  [    3.399934]  _freq_tbl_determine_rate+0x48/0x100\n  [    3.404753]  clk_rcg2_determine_rate+0x1c/0x28\n  [    3.409387]  clk_core_determine_round_nolock+0x58/0xe4\n  [    3.421414]  clk_core_round_rate_nolock+0x48/0xfc\n  [    3.432974]  clk_core_round_rate_nolock+0xd0/0xfc\n  [    3.444483]  clk_core_set_rate_nolock+0x8c/0x300\n  [    3.455886]  clk_set_rate+0x38/0x14c\n\nAdd the parent_map property for two clocks where it's missing and also\nun-inline the parent_data as well to keep the matching parent_map and\nparent_data together.\n\ud83d\udccf Published: 2025-03-06T16:13:40.307Z\n\ud83d\udccf Modified: 2025-05-04T10:09:26.165Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/175af15551ed5aa6af16ff97aff75cfffb42da21\n2. https://git.kernel.org/stable/c/39336edd14a59dc086fb19957655e0f340bb28e8\n3. https://git.kernel.org/stable/c/08b77ed7cfaac62bba51ac7a0487409ec9fcbc84\n4. https://git.kernel.org/stable/c/b6fe13566bf5676b1e3b72d2a06d875733e93ee6\n5. https://git.kernel.org/stable/c/3e567032233a240b903dc11c9f18eeb3faa10ffa\n6. https://git.kernel.org/stable/c/96fe1a7ee477d701cfc98ab9d3c730c35d966861", "creation_timestamp": "2025-05-04T11:19:13.000000Z"}, {"uuid": "9cf19ab6-a940-4040-9902-e5985b1003e1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-58077", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14791", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-58077\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: soc-pcm: don't use soc_pcm_ret() on .prepare callback\n\ncommit 1f5664351410 (\"ASoC: lower \"no backend DAIs enabled for ... Port\"\nlog severity\") ignores -EINVAL error message on common soc_pcm_ret().\nIt is used from many functions, ignoring -EINVAL is over-kill.\n\nThe reason why -EINVAL was ignored was it really should only be used\nupon invalid parameters coming from userspace and in that case we don't\nwant to log an error since we do not want to give userspace a way to do\na denial-of-service attack on the syslog / diskspace.\n\nSo don't use soc_pcm_ret() on .prepare callback is better idea.\n\ud83d\udccf Published: 2025-03-06T16:13:41.159Z\n\ud83d\udccf Modified: 2025-05-04T10:09:27.591Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/b65ba768302adc7ddc70811116cef80ca089af59\n2. https://git.kernel.org/stable/c/79b8c7c93beb4f5882c9ee5b9ba73354fa4bc9ee\n3. https://git.kernel.org/stable/c/90778f31efdf44622065ebbe8d228284104bd26f\n4. https://git.kernel.org/stable/c/8ec4e8c8e142933eaa8e1ed87168831069250e4e\n5. https://git.kernel.org/stable/c/301c26a018acb94dd537a4418cefa0f654500c6f", "creation_timestamp": "2025-05-04T11:19:12.000000Z"}, {"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"}, {"uuid": "46656661-848b-4e6f-a259-4ca2c14456ed", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-58078", "type": "seen", "source": "https://t.me/cvedetector/19725", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-58078 - Linux Kernel Misc Dynamic Minor Allocation IDA Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-58078 \nPublished : March 6, 2025, 5:15 p.m. | 1\u00a0hour ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nmisc: misc_minor_alloc to use ida for all dynamic/misc dynamic minors  \n  \nmisc_minor_alloc was allocating id using ida for minor only in case of  \nMISC_DYNAMIC_MINOR but misc_minor_free was always freeing ids  \nusing ida_free causing a mismatch and following warn:  \n> > WARNING: CPU: 0 PID: 159 at lib/idr.c:525 ida_free+0x3e0/0x41f  \n> > ida_free called for id=127 which is not allocated.  \n> > <<> [<60941eb4] ida_free+0x3e0/0x41f  \n> > [<605ac993] misc_minor_free+0x3e/0xbc  \n> > [<605acb82] misc_deregister+0x171/0x1b3  \n  \nmisc_minor_alloc is changed to allocate id from ida for all minors  \nfalling in the range of dynamic/ misc dynamic minors \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:46.000000Z"}, {"uuid": "39bee862-1e7b-4e65-9e99-dae82e89a18c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-5807", "type": "seen", "source": "https://t.me/cvedetector/1986", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-5807 - WordPress Business Card Plugin Remote Code Execution Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-5807 \nPublished : July 30, 2024, 6:15 a.m. | 40\u00a0minutes ago \nDescription : The Business Card WordPress plugin through 1.0.0 does not prevent high privilege users like administrators from uploading malicious PHP files, which could allow them to run arbitrary code on servers hosting their site, even in MultiSite configurations. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"30 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-30T09:02:45.000000Z"}, {"uuid": "43d34e4a-b7d1-4892-9f75-803ab21c188d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-5807", "type": "seen", "source": "Telegram/rnSeUs2qdya-yEinROFxA8N7F3mjvuSNXUGSd_-xczm3plg", "content": "", "creation_timestamp": "2025-01-31T14:10:05.000000Z"}, {"uuid": "317e0ea0-edcd-4fdd-9da5-bb47215d9dfb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-58075", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14793", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-58075\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: tegra - do not transfer req when tegra init fails\n\nThe tegra_cmac_init or tegra_sha_init function may return an error when\nmemory is exhausted. It should not transfer the request when they return\nan error.\n\ud83d\udccf Published: 2025-03-06T16:04:30.864Z\n\ud83d\udccf Modified: 2025-05-04T10:09:24.851Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/1dbc270f9df7f0ae1e591323431869059cee1b7d\n2. https://git.kernel.org/stable/c/5eaa7c916e1ec4b122a1c3a8a20e692d9d9e174e\n3. https://git.kernel.org/stable/c/15589bda46830695a3261518bb7627afac61f519", "creation_timestamp": "2025-05-04T11:19:14.000000Z"}, {"uuid": "44e2ab26-3173-4e3f-9873-2ff0d4bd8344", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-58079", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3ljqbkhb4v72f", "content": "", "creation_timestamp": "2025-03-06T19:54:49.288852Z"}, {"uuid": "4fb7e872-2165-4d68-beba-c8c2f12e17d6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-58077", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3ljqbkhi7mb2q", "content": "", "creation_timestamp": "2025-03-06T19:54:50.369016Z"}, {"uuid": "586f26b2-91a6-4b7c-88b7-6dcf878a75ff", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2024-58077", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "c0bc8139-4a9f-4962-bbcb-92c46613bb82", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-58079", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14790", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-58079\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: 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.\n\ud83d\udccf Published: 2025-03-06T16:13:42.640Z\n\ud83d\udccf Modified: 2025-05-04T10:09:30.587Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/0fdd7cc593385e46e92e180b71e264fc9c195298\n2. https://git.kernel.org/stable/c/3c00e94d00ca079bef7906d6f39d1091bccfedd3\n3. https://git.kernel.org/stable/c/0b5e0445bc8384c18bd35cb9fe87f6258c6271d9\n4. https://git.kernel.org/stable/c/d2eac8b14ac690aa73052aa6d4ba69005715367e\n5. https://git.kernel.org/stable/c/5d2e65cbe53d0141ed095cf31c2dcf3d8668c11d\n6. https://git.kernel.org/stable/c/a9ea1a3d88b7947ce8cadb2afceee7a54872bbc5", "creation_timestamp": "2025-05-04T11:19:10.000000Z"}, {"uuid": "241f9f12-1b37-4092-8c4e-faea9954306d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-58072", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14796", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-58072\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtlwifi: remove unused check_buddy_priv\n\nCommit 2461c7d60f9f (\"rtlwifi: Update header file\") introduced a global\nlist of private data structures.\n\nLater on, commit 26634c4b1868 (\"rtlwifi Modify existing bits to match\nvendor version 2013.02.07\") started adding the private data to that list at\nprobe time and added a hook, check_buddy_priv to find the private data from\na similar device.\n\nHowever, that function was never used.\n\nBesides, though there is a lock for that list, it is never used. And when\nthe probe fails, the private data is never removed from the list. This\nwould cause a second probe to access freed memory.\n\nRemove the unused hook, structures and members, which will prevent the\npotential race condition on the list and its corruption during a second\nprobe when probe fails.\n\ud83d\udccf Published: 2025-03-06T15:54:11.665Z\n\ud83d\udccf Modified: 2025-05-04T10:09:20.322Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/f801e754efa21bd61b3cc15ec7565696165b272f\n2. https://git.kernel.org/stable/c/1b9cbd8a9ae68b32099fbb03b2d5ffa0c5e0dcc9\n3. https://git.kernel.org/stable/c/8e2fcc68fbaab3ad9f5671fee2be0956134b740a\n4. https://git.kernel.org/stable/c/1e39b0486cdb496cdfba3bc89886150e46acf6f4\n5. https://git.kernel.org/stable/c/465d01ef6962b82b1f0ad1f3e58b398dbd35c1c1\n6. https://git.kernel.org/stable/c/543e3e9f2e9e47ded774c74e680f28a0ca362aee\n7. https://git.kernel.org/stable/c/006e803af7408c3fc815b0654fc5ab43d34f0154\n8. https://git.kernel.org/stable/c/2fdac64c3c35858aa8ac5caa70b232e03456e120", "creation_timestamp": "2025-05-04T11:19:20.000000Z"}, {"uuid": "6f29c26d-cad6-447b-bdb2-bd99149c483e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-58073", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14795", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-58073\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/msm/dpu: check dpu_plane_atomic_print_state() for valid sspp\n\nSimilar to the r_pipe sspp protect, add a check to protect\nthe pipe state prints to avoid NULL ptr dereference for cases when\nthe state is dumped without a corresponding atomic_check() where the\npipe->sspp is assigned.\n\nPatchwork: https://patchwork.freedesktop.org/patch/628404/\n\ud83d\udccf Published: 2025-03-06T15:54:12.374Z\n\ud83d\udccf Modified: 2025-05-04T10:09:21.884Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/008af2074e4b91d34440102501b710c235a3b245\n2. https://git.kernel.org/stable/c/789384eb1437aed94155dc0eac8a8a6ba1baf578", "creation_timestamp": "2025-05-04T11:19:16.000000Z"}, {"uuid": "08ff4b88-451c-4a01-b47e-2db619a116ea", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-58074", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14794", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-58074\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/i915: Grab intel_display from the encoder to avoid potential oopsies\n\nGrab the intel_display from 'encoder' rather than 'state'\nin the encoder hooks to avoid the massive footgun that is\nintel_sanitize_encoder(), which passes NULL as the 'state'\nargument to encoder .disable() and .post_disable().\n\nTODO: figure out how to actually fix intel_sanitize_encoder()...\n\ud83d\udccf Published: 2025-03-06T16:04:30.170Z\n\ud83d\udccf Modified: 2025-05-04T10:09:23.193Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/1885401569f24eb35c631bcc4e6543360dbe9292\n2. https://git.kernel.org/stable/c/dc3806d9eb66d0105f8d55d462d4ef681d9eac59", "creation_timestamp": "2025-05-04T11:19:15.000000Z"}, {"uuid": "dc09ac40-4556-4b9f-a318-a59a8b0e861d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-58077", "type": "seen", "source": "https://t.me/cvedetector/19730", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-58077 - Linux Kernel ASoC soc_pcm Denial-of-Service Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-58077 \nPublished : March 6, 2025, 5:15 p.m. | 1\u00a0hour ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nASoC: soc-pcm: don't use soc_pcm_ret() on .prepare callback  \n  \ncommit 1f5664351410 (\"ASoC: lower \"no backend DAIs enabled for ... Port\"  \nlog severity\") ignores -EINVAL error message on common soc_pcm_ret().  \nIt is used from many functions, ignoring -EINVAL is over-kill.  \n  \nThe reason why -EINVAL was ignored was it really should only be used  \nupon invalid parameters coming from userspace and in that case we don't  \nwant to log an error since we do not want to give userspace a way to do  \na denial-of-service attack on the syslog / diskspace.  \n  \nSo don't use soc_pcm_ret() on .prepare callback is better idea. \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:53.000000Z"}]}