tick/broadcast: Move per CPU pointer access into the atomic section
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3a58c590f6bd1d20eb1e76c5cea31c36cc032339 · < b9d604933d5fd72dd37f24e1dc35f778297d745a| No fix yet |
| Linux Linux |
| No fix yet |
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.
From the CVE record · Linux
The Linux kernel's broadcast timer takeover code can access a per-CPU pointer in preemptible context, triggering a BUG warning. The input does not describe an attacker-controlled path, authentication requirements, or user interaction.
Anyone running the Linux kernel should check whether their version includes the fix; affected versions are not specified.