{"uuid": "4fc2d1b7-b492-4f79-add1-d67fe4b02d63", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21996", "type": "seen", "source": "https://t.me/cvedetector/21964", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21996 - Radeon Linux Kernel Uninitialized Variable Use\", \n  \"Content\": \"CVE ID : CVE-2025-21996 \nPublished : April 3, 2025, 8:15 a.m. | 38\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/radeon: fix uninitialized size issue in radeon_vce_cs_parse()  \n  \nOn the off chance that command stream passed from userspace via  \nioctl() call to radeon_vce_cs_parse() is weirdly crafted and  \nfirst command to execute is to encode (case 0x03000001), the function  \nin question will attempt to call radeon_vce_cs_reloc() with size  \nargument that has not been properly initialized. Specifically, 'size'  \nwill point to 'tmp' variable before the latter had a chance to be  \nassigned any value.  \n  \nPlay it safe and init 'tmp' with 0, thus ensuring that  \nradeon_vce_cs_reloc() will catch an early error in cases like these.  \n  \nFound by Linux Verification Center (linuxtesting.org) with static  \nanalysis tool SVACE.  \n  \n(cherry picked from commit 2d52de55f9ee7aaee0e09ac443f77855989c6b68) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"03 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-03T11:03:26.000000Z"}