https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 14:18:39 +0000 https://vulnerability.circl.lu/vuln/cve-2024-44968 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>tick/broadcast: Move per CPU pointer access into the atomic section</p> <p>The recent fix for making the take over of the broadcast timer more reliable retrieves a per CPU pointer in preemptible context.</p> <p>This went unnoticed as compilers hoist the access into the non-preemptible region where the pointer is actually used. But of course it&#39;s valid that the compiler keeps it at the place where the code puts it which rightfully triggers:</p> <p>BUG: using smp_processor_id() in preemptible [00000000] code: caller is hotplug_cpu__broadcast_tick_pull+0x1c/0xc0</p> <p>Move it to the actual usage site which is in a non-preemptible region.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>tick/broadcast: Move per CPU pointer access into the atomic section</p> <p>The recent fix for making the take over of the broadcast timer more reliable retrieves a per CPU pointer in preemptible context.</p> <p>This went unnoticed as compilers hoist the access into the non-preemptible region where the pointer is actually used. But of course it&#39;s valid that the compiler keeps it at the place where the code puts it which rightfully triggers:</p> <p>BUG: using smp_processor_id() in preemptible [00000000] code: caller is hotplug_cpu__broadcast_tick_pull+0x1c/0xc0</p> <p>Move it to the actual usage site which is in a non-preemptible region.</p> https://vulnerability.circl.lu/vuln/cve-2024-44968