{"uuid": "3995fe9a-ab0a-47ce-9761-19c4bac76fef", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46871", "type": "seen", "source": "https://t.me/cvedetector/7467", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-46871 - \"AMDGPU_DMUB_NOTIFICATION_MAX Array Out-of-Bounds Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-46871 \nPublished : Oct. 9, 2024, 2:15 p.m. | 38\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/amd/display: Correct the defined value for AMDGPU_DMUB_NOTIFICATION_MAX  \n  \n[Why &amp; How]  \nIt actually exposes '6' types in enum dmub_notification_type. Not 5. Using smaller  \nnumber to create array dmub_callback &amp; dmub_thread_offload has potential to access  \nitem out of array bound. Fix it. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-09T17:19:10.000000Z"}