{"vulnerability": "CVE-2024-46693", "sightings": [{"uuid": "02ee1300-735c-4e84-a8ab-c8f70b776486", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46693", "type": "seen", "source": "https://t.me/cvedetector/5549", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-46693 - Qualcomm QCOM Linux Kernel NULL Pointer Dereference\", \n  \"Content\": \"CVE ID : CVE-2024-46693 \nPublished : Sept. 13, 2024, 6:15 a.m. | 29\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nsoc: qcom: pmic_glink: Fix race during initialization  \n  \nAs pointed out by Stephen Boyd it is possible that during initialization  \nof the pmic_glink child drivers, the protection-domain notifiers fires,  \nand the associated work is scheduled, before the client registration  \nreturns and as a result the local \"client\" pointer has been initialized.  \n  \nThe outcome of this is a NULL pointer dereference as the \"client\"  \npointer is blindly dereferenced.  \n  \nTimeline provided by Stephen:  \n CPU0                               CPU1  \n ----                               ----  \n ucsi-&gt;client = NULL;  \n devm_pmic_glink_register_client()  \n  client-&gt;pdr_notify(client-&gt;priv, pg-&gt;client_state)  \n   pmic_glink_ucsi_pdr_notify()  \n    schedule_work(&amp;ucsi-&gt;register_work)  \n      \n                                    pmic_glink_ucsi_register()  \n                                     ucsi_register()  \n                                      pmic_glink_ucsi_read_version()  \n                                       pmic_glink_ucsi_read()  \n                                        pmic_glink_ucsi_read()  \n                                         pmic_glink_send(ucsi-&gt;client)  \n                                           \n ucsi-&gt;client = client // Too late!  \n  \nThis code is identical across the altmode, battery manager and usci  \nchild drivers.  \n  \nResolve this by splitting the allocation of the \"client\" object and the  \nregistration thereof into two operations.  \n  \nThis only happens if the protection domain registry is populated at the  \ntime of registration, which by the introduction of commit '1ebcde047c54  \n(\"soc: qcom: add pd-mapper implementation\")' became much more likely. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"13 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-13T08:45:47.000000Z"}]}