CVE-2024-44968

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

MEDIUM

5.5

CVSS Score

Published: September 4, 2024 at 06:56 PM UTC

Updated: June 17, 2026 at 07:53 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

6.1.103 ≤ v < 6.1.1056.10.3 ≤ v < 6.10.56.6.44 ≤ v < 6.6.462cdab4b4bf77369961f706cdeb7d040db10c52173a58c590f6bd1d20eb1e76c5cea31c36cc032339408bfb6b0a7f22e971ce6b600aec448769e580a8457a1c87d454455d671a3045cf0b56157be110a16.1.103 6.10.3 6.11 rc1 6.6.449ef7190228145f959d9bc0ddca40ecf76bb413b0d3b165c10473aa6fc6141bb5b1f6e5b50c1fb774dfe19aa91378972f10530635ad83b2d77f481044f7d43dd206e7e18c182f200e67a8db8c209907fa

Vendor states this is fixed in 541a900d245536d4809cb1aa322c3fcc2cdb58a6 (fixed)

Vendor states this is fixed in 668c6c4a7e9e9f081c06b70f30104fb7013437ed (fixed)

Vendor states this is fixed in 6881e75237a84093d0986f56223db3724619f26e (fixed)

Vendor states this is fixed in 7b3ec186ba93e333e9efe7254e7e31c1828e5d2d (fixed)

Vendor states this is fixed in 7dd12f85f150010ef7518201c63fa7e395f5c3e9 (fixed)

Vendor states this is fixed in b9d604933d5fd72dd37f24e1dc35f778297d745a (fixed)

Vendor states this is fixed in f54abf332a2bc0413cfa8bd6a8511f7aa99faea0 (fixed)

Vendor states this is fixed in f91fb47ecacc178a83a77eeebd25cbaec18c01d6 (fixed)

Affected range stops below 6.1.105, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.10.5, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.6.46, so it looks safe — our inference, not a vendor statement