Skip to main content
← All vulnerabilities
CVE-2024-44968

tick/broadcast: Move per CPU pointer access into the atomic section

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 6.1.105, 6.6.46, 6.10.5
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

In the Linux kernel, the following vulnerability has been resolved: tick/broadcast: Move per CPU pointer access into the atomic section The recent fix for making the take over of the broadcast timer more reliable retrieves a per CPU pointer in preemptible context. This went unnoticed as compilers hoist the access into the non-preemptible region where the pointer is actually used. But of course it's valid that the compiler keeps it at the place where the code puts it which rightfully triggers: BUG: using smp_processor_id() in preemptible [00000000] code: caller is hotplug_cpu__broadcast_tick_pull+0x1c/0xc0 Move it to the actual usage site which is in a non-preemptible region.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  3. Record last updated

Affected versions

  • Linux Linux

    Version range not reported

  • Linux Linux

    From 6.1.103 · fixed in 6.1.105; From 6.6.44 · fixed in 6.6.46; From 6.10.3 · fixed in 6.10.5

References 8

git.kernel.org