https://vulnerability.circl.lu/sightings/feed 2026-05-09T13:23:33.066291+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/1da03a6f-a080-4c94-a719-b45256ae410e/export 2026-05-09T13:23:33.450287+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "1da03a6f-a080-4c94-a719-b45256ae410e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-58084", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/6707", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-58084\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool()\n\nCommit 2e4955167ec5 (\"firmware: qcom: scm: Fix __scm and waitq\ncompletion variable initialization\") introduced a write barrier in probe\nfunction to store global '__scm' variable. We all known barriers are\npaired (see memory-barriers.txt: \"Note that write barriers should\nnormally be paired with read or address-dependency barriers\"), therefore\naccessing it from concurrent contexts requires read barrier. Previous\ncommit added such barrier in qcom_scm_is_available(), so let's use that\ndirectly.\n\nLack of this read barrier can result in fetching stale '__scm' variable\nvalue, NULL, and dereferencing it.\n\nNote that barrier in qcom_scm_is_available() satisfies here the control\ndependency.\n\ud83d\udccf Published: 2025-03-06T16:22:31.998Z\n\ud83d\udccf Modified: 2025-03-06T16:22:31.998Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/fee921e3c641f64185abee83f9a6e65f0b380682\n2. https://git.kernel.org/stable/c/e03db7c1255ebabba5e1a447754faeb138de15a2\n3. https://git.kernel.org/stable/c/b628510397b5cafa1f5d3e848a28affd1c635302", "creation_timestamp": "2025-03-06T16:34:07.000000Z"} 2025-03-06T16:34:07+00:00 https://vulnerability.circl.lu/sighting/0824fddd-9046-4e3f-855c-acf9aeb0372c/export 2026-05-09T13:23:33.450151+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "0824fddd-9046-4e3f-855c-acf9aeb0372c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-58084", "type": "seen", "source": "https://t.me/cvedetector/19731", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-58084 - Qualcomm QCOM Firmware Read Barrier Vulnerability (Data Corruption)\", \n \"Content\": \"CVE ID : CVE-2024-58084 \nPublished : March 6, 2025, 5:15 p.m. | 1\u00a0hour ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nfirmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool() \n \nCommit 2e4955167ec5 (\"firmware: qcom: scm: Fix __scm and waitq \ncompletion variable initialization\") introduced a write barrier in probe \nfunction to store global '__scm' variable. We all known barriers are \npaired (see memory-barriers.txt: \"Note that write barriers should \nnormally be paired with read or address-dependency barriers\"), therefore \naccessing it from concurrent contexts requires read barrier. Previous \ncommit added such barrier in qcom_scm_is_available(), so let's use that \ndirectly. \n \nLack of this read barrier can result in fetching stale '__scm' variable \nvalue, NULL, and dereferencing it. \n \nNote that barrier in qcom_scm_is_available() satisfies here the control \ndependency. \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:54.000000Z"} 2025-03-06T19:41:54+00:00 https://vulnerability.circl.lu/sighting/50418220-2aaa-44f7-8b22-0ebdd5ebafd9/export 2026-05-09T13:23:33.447926+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "50418220-2aaa-44f7-8b22-0ebdd5ebafd9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-58084", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14786", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-58084\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool()\n\nCommit 2e4955167ec5 (\"firmware: qcom: scm: Fix __scm and waitq\ncompletion variable initialization\") introduced a write barrier in probe\nfunction to store global '__scm' variable. We all known barriers are\npaired (see memory-barriers.txt: \"Note that write barriers should\nnormally be paired with read or address-dependency barriers\"), therefore\naccessing it from concurrent contexts requires read barrier. Previous\ncommit added such barrier in qcom_scm_is_available(), so let's use that\ndirectly.\n\nLack of this read barrier can result in fetching stale '__scm' variable\nvalue, NULL, and dereferencing it.\n\nNote that barrier in qcom_scm_is_available() satisfies here the control\ndependency.\n\ud83d\udccf Published: 2025-03-06T16:22:31.998Z\n\ud83d\udccf Modified: 2025-05-04T10:09:42.783Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/fee921e3c641f64185abee83f9a6e65f0b380682\n2. https://git.kernel.org/stable/c/e03db7c1255ebabba5e1a447754faeb138de15a2\n3. https://git.kernel.org/stable/c/b628510397b5cafa1f5d3e848a28affd1c635302", "creation_timestamp": "2025-05-04T11:19:05.000000Z"} 2025-05-04T11:19:05+00:00