๐Ÿ” CVE Alert

CVE-2024-44968

UNKNOWN 0.0

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

CVSS Score
0.0
EPSS Score
0.0%
EPSS Percentile
0th

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.

Vendor linux
Product linux
Ecosystems
Industries
Technology
Published Sep 4, 2024
Last Updated May 11, 2026
Stay Ahead of the Next One

Get instant alerts for linux linux

Be the first to know when new unknown vulnerabilities affecting linux linux are published โ€” delivered to Slack, Telegram or Discord.

Get Free Alerts โ†’ Free ยท No credit card ยท 60 sec setup

Affected Versions

Linux / Linux
dfe19aa91378972f10530635ad83b2d77f481044 < f54abf332a2bc0413cfa8bd6a8511f7aa99faea0 457a1c87d454455d671a3045cf0b56157be110a1 < f91fb47ecacc178a83a77eeebd25cbaec18c01d6 9ef7190228145f959d9bc0ddca40ecf76bb413b0 < 668c6c4a7e9e9f081c06b70f30104fb7013437ed d3b165c10473aa6fc6141bb5b1f6e5b50c1fb774 < 541a900d245536d4809cb1aa322c3fcc2cdb58a6 408bfb6b0a7f22e971ce6b600aec448769e580a8 < 7b3ec186ba93e333e9efe7254e7e31c1828e5d2d 3a58c590f6bd1d20eb1e76c5cea31c36cc032339 < b9d604933d5fd72dd37f24e1dc35f778297d745a 2cdab4b4bf77369961f706cdeb7d040db10c5217 < 7dd12f85f150010ef7518201c63fa7e395f5c3e9 f7d43dd206e7e18c182f200e67a8db8c209907fa < 6881e75237a84093d0986f56223db3724619f26e
Linux / Linux
6.1.103 < 6.1.105 6.6.44 < 6.6.46 6.10.3 < 6.10.5

References

NVD โ†— CVE.org โ†— EPSS Data โ†—
git.kernel.org: https://git.kernel.org/stable/c/f54abf332a2bc0413cfa8bd6a8511f7aa99faea0 git.kernel.org: https://git.kernel.org/stable/c/f91fb47ecacc178a83a77eeebd25cbaec18c01d6 git.kernel.org: https://git.kernel.org/stable/c/668c6c4a7e9e9f081c06b70f30104fb7013437ed git.kernel.org: https://git.kernel.org/stable/c/541a900d245536d4809cb1aa322c3fcc2cdb58a6 git.kernel.org: https://git.kernel.org/stable/c/7b3ec186ba93e333e9efe7254e7e31c1828e5d2d git.kernel.org: https://git.kernel.org/stable/c/b9d604933d5fd72dd37f24e1dc35f778297d745a git.kernel.org: https://git.kernel.org/stable/c/7dd12f85f150010ef7518201c63fa7e395f5c3e9 git.kernel.org: https://git.kernel.org/stable/c/6881e75237a84093d0986f56223db3724619f26e lists.debian.org: https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html lists.debian.org: https://lists.debian.org/debian-lts-announce/2024/10/msg00003.html