https://vulnerability.circl.lu/sightings/feed 2026-06-02T03:32:58.406894+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/165a442f-881e-4d9f-8834-6aaef0f86c3f/export 2026-06-02T03:32:58.883706+00:00 Automation user https://cve.circl.lu/user/automation {"uuid": "165a442f-881e-4d9f-8834-6aaef0f86c3f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-44968", "type": "seen", "source": "https://t.me/cvedetector/4835", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-44968 - Linux Kernel CPU Pointer Access Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-44968 \nPublished : Sept. 4, 2024, 7:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ntick/broadcast: Move per CPU pointer access into the atomic section \n \nThe recent fix for making the take over of the broadcast timer more \nreliable retrieves a per CPU pointer in preemptible context. \n \nThis went unnoticed as compilers hoist the access into the non-preemptible \nregion where the pointer is actually used. But of course it's valid that \nthe compiler keeps it at the place where the code puts it which rightfully \ntriggers: \n \n BUG: using smp_processor_id() in preemptible [00000000] code: \n caller is hotplug_cpu__broadcast_tick_pull+0x1c/0xc0 \n \nMove it to the actual usage site which is in a non-preemptible region. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"04 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-04T21:56:10.000000Z"} 2024-09-04T21:56:10+00:00