https://vulnerability.circl.lu/sightings/feed 2026-05-08T13:10:28.335019+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/e980874e-2475-4b10-906a-cef253227659/export 2026-05-08T13:10:28.792654+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "e980874e-2475-4b10-906a-cef253227659", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50203", "type": "seen", "source": "https://t.me/cvedetector/10180", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-50203 - Linux Kernel bpf Arm64 Heap Buffer Overflow\", \n \"Content\": \"CVE ID : CVE-2024-50203 \nPublished : Nov. 8, 2024, 6:15 a.m. | 41\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nbpf, arm64: Fix address emission with tag-based KASAN enabled \n \nWhen BPF_TRAMP_F_CALL_ORIG is enabled, the address of a bpf_tramp_image \nstruct on the stack is passed during the size calculation pass and \nan address on the heap is passed during code generation. This may \ncause a heap buffer overflow if the heap address is tagged because \nemit_a64_mov_i64() will emit longer code than it did during the size \ncalculation pass. The same problem could occur without tag-based \nKASAN if one of the 16-bit words of the stack address happened to \nbe all-ones during the size calculation pass. Fix the problem by \nassuming the worst case (4 instructions) when calculating the size \nof the bpf_tramp_image address emission. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"08 Nov 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-08T07:59:56.000000Z"} 2024-11-08T07:59:56+00:00