{"vulnerability": "CVE-2024-50156", "sightings": [{"uuid": "fd553e88-60be-47dc-8184-aa1e8e0071a5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-50156", "type": "seen", "source": "https://t.me/cvedetector/10079", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50156 - Android MSM DRM Null Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-50156 \nPublished : Nov. 7, 2024, 10:15 a.m. | 34\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/msm: Avoid NULL dereference in msm_disp_state_print_regs()  \n  \nIf the allocation in msm_disp_state_dump_regs() failed then  \n`block->state` can be NULL. The msm_disp_state_print_regs() function  \n_does_ have code to try to handle it with:  \n  \n  if (*reg)  \n    dump_addr = *reg;  \n  \n...but since \"dump_addr\" is initialized to NULL the above is actually  \na noop. The code then goes on to dereference `dump_addr`.  \n  \nMake the function print \"Registers not stored\" when it sees a NULL to  \nsolve this. Since we're touching the code, fix  \nmsm_disp_state_print_regs() not to pointlessly take a double-pointer  \nand properly mark the pointer as `const`.  \n  \nPatchwork:  \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"07 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-07T11:54:38.000000Z"}, {"uuid": "26cc8bfa-b929-418c-ba34-348185262fc9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-50156", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113441232433416909", "content": "", "creation_timestamp": "2024-11-07T10:37:17.231362Z"}]}