CVE-2024-44968 json
tick/broadcast: Move per CPU pointer access into the atomic section
published 2024-09-04 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-41170
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
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.
Patch / fix
- Linux Linux 6.1.105, 6.6.46, 6.10.5
- linux Debian 12 6.1.106-1
- linux Debian 14, Debian 13 6.10.6-1
debian advisories DEBIAN-CVE-2024-44968
- git.kernel.org/stable/c/f54abf332a2bc0413cfa8bd6a8511f7aa99faea0 commit
- git.kernel.org/stable/c/f91fb47ecacc178a83a77eeebd25cbaec18c01d6 commit
- git.kernel.org/stable/c/668c6c4a7e9e9f081c06b70f30104fb7013437ed commit
- git.kernel.org/stable/c/541a900d245536d4809cb1aa322c3fcc2cdb58a6 commit
- git.kernel.org/stable/c/7b3ec186ba93e333e9efe7254e7e31c1828e5d2d commit
- git.kernel.org/stable/c/b9d604933d5fd72dd37f24e1dc35f778297d745a commit
- git.kernel.org/stable/c/7dd12f85f150010ef7518201c63fa7e395f5c3e9 commit
- git.kernel.org/stable/c/6881e75237a84093d0986f56223db3724619f26e commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-44968 updated cvss 4.4
kernel: tick/broadcast: Move per CPU pointer access into the atomic section
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/f54abf332a2bc0413cfa8bd6a8511f7aa99faea0
patch
-
git.kernel.org
/stable/c/f91fb47ecacc178a83a77eeebd25cbaec18c01d6
patch
-
git.kernel.org
/stable/c/668c6c4a7e9e9f081c06b70f30104fb7013437ed
patch
-
git.kernel.org
/stable/c/541a900d245536d4809cb1aa322c3fcc2cdb58a6
patch
-
git.kernel.org
/stable/c/7b3ec186ba93e333e9efe7254e7e31c1828e5d2d
patch
-
git.kernel.org
/stable/c/b9d604933d5fd72dd37f24e1dc35f778297d745a
patch
-
git.kernel.org
/stable/c/7dd12f85f150010ef7518201c63fa7e395f5c3e9
patch
-
git.kernel.org
/stable/c/6881e75237a84093d0986f56223db3724619f26e
patch
- lists.debian.org /debian-lts-announce/2025/01/msg00001.html
- lists.debian.org /debian-lts-announce/2024/10/msg00003.html
Sources
- CVE List CVE-2024-44968
- NVD CVE-2024-44968
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.