https://vulnerability.circl.lu/sightings/feed 2026-05-08T07:35:59.093275+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/1d59d104-1804-4a9e-9be2-454ce2d761f9/export 2026-05-08T07:35:59.482372+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "1d59d104-1804-4a9e-9be2-454ce2d761f9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-43851", "type": "seen", "source": "https://t.me/cvedetector/3419", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-43851 - Xilinx Soc Linux Kernel Device ID Renaming Information Disclosure Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-43851 \nPublished : Aug. 17, 2024, 10:15 a.m. | 41\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nsoc: xilinx: rename cpu_number1 to dummy_cpu_number \n \nThe per cpu variable cpu_number1 is passed to xlnx_event_handler as \nargument \"dev_id\", but it is not used in this function. So drop the \ninitialization of this variable and rename it to dummy_cpu_number. \nThis patch is to fix the following call trace when the kernel option \nCONFIG_DEBUG_ATOMIC_SLEEP is enabled: \n \nBUG: sleeping function called from invalid context at include/linux/sched/mm.h:274 \n in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: swapper/0 \n preempt_count: 1, expected: 0 \n CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.1.0 #53 \n Hardware name: Xilinx Versal vmk180 Eval board rev1.1 (QSPI) (DT) \n Call trace: \n dump_backtrace+0xd0/0xe0 \n show_stack+0x18/0x40 \n dump_stack_lvl+0x7c/0xa0 \n dump_stack+0x18/0x34 \n __might_resched+0x10c/0x140 \n __might_sleep+0x4c/0xa0 \n __kmem_cache_alloc_node+0xf4/0x168 \n kmalloc_trace+0x28/0x38 \n __request_percpu_irq+0x74/0x138 \n xlnx_event_manager_probe+0xf8/0x298 \n platform_probe+0x68/0xd8 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"17 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-17T13:09:11.000000Z"} 2024-08-17T13:09:11+00:00