{"vulnerability": "CVE-2025-21985", "sightings": [{"uuid": "779d6fb0-8d2a-49ae-9a99-8b95c1c59e0e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21985", "type": "seen", "source": "https://t.me/cvedetector/21787", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21985 - AMD Display Out-of-Bounds Array Index Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21985 \nPublished : April 1, 2025, 4:15 p.m. | 1\u00a0hour, 15\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/amd/display: Fix out-of-bound accesses  \n  \n[WHAT &amp; HOW]  \nhpo_stream_to_link_encoder_mapping has size MAX_HPO_DP2_ENCODERS(=4),  \nbut location can have size up to 6. As a result, it is necessary to  \ncheck location against MAX_HPO_DP2_ENCODERS.  \n  \nSimiliarly, disp_cfg_stream_location can be used as an array index which  \nshould be 0..5, so the ASSERT's conditions should be less without equal. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-01T19:44:32.000000Z"}, {"uuid": "8ba2b583-e6b2-4606-a4f2-16115d0a1156", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-21985", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "c63dad18-8936-4723-87cd-d3e543dc768c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2025-21985", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}]}