{"uuid": "09d9fc53-daf6-45f0-8eb5-5171ce6022b2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57800", "type": "seen", "source": "https://t.me/cvedetector/15058", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57800 - ALSA DMA API Error Handling Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-57800 \nPublished : Jan. 11, 2025, 1:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nALSA: memalloc: prefer dma_mapping_error() over explicit address checking  \n  \nWith CONFIG_DMA_API_DEBUG enabled, the following warning is observed:  \n  \nDMA-API: snd_hda_intel 0000:03:00.1: device driver failed to check map error[device address=0x00000000ffff0000] [size=20480 bytes] [mapped as single]  \nWARNING: CPU: 28 PID: 2255 at kernel/dma/debug.c:1036 check_unmap+0x1408/0x2430  \nCPU: 28 UID: 42 PID: 2255 Comm: wireplumber Tainted: G  W L  6.12.0-10-133577cad6bf48e5a7848c4338124081393bfe8a+ #759  \ndebug_dma_unmap_page+0xe9/0xf0  \nsnd_dma_wc_free+0x85/0x130 [snd_pcm]  \nsnd_pcm_lib_free_pages+0x1e3/0x440 [snd_pcm]  \nsnd_pcm_common_ioctl+0x1c9a/0x2960 [snd_pcm]  \nsnd_pcm_ioctl+0x6a/0xc0 [snd_pcm]  \n...  \n  \nCheck for returned DMA addresses using specialized dma_mapping_error()  \nhelper which is generally recommended for this purpose by  \nDocumentation/core-api/dma-api.rst. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"11 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-11T14:55:08.000000Z"}