Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-44968tick/broadcast: Move per CPU pointer access into the atomic section

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.

Timeline

  1. ID reserved

    By Linux

  2. · 14 days later

    Published

  3. · 20 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-44968, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected dfe19aa91378972f10530635ad83b2d77f481044 – < f54abf332a2bc0413cfa8bd6a8511f7aa99faea0
    • affected 457a1c87d454455d671a3045cf0b56157be110a1 – < f91fb47ecacc178a83a77eeebd25cbaec18c01d6
    • affected 9ef7190228145f959d9bc0ddca40ecf76bb413b0 – < 668c6c4a7e9e9f081c06b70f30104fb7013437ed
    • affected d3b165c10473aa6fc6141bb5b1f6e5b50c1fb774 – < 541a900d245536d4809cb1aa322c3fcc2cdb58a6
    • affected 408bfb6b0a7f22e971ce6b600aec448769e580a8 – < 7b3ec186ba93e333e9efe7254e7e31c1828e5d2d
    • affected 3a58c590f6bd1d20eb1e76c5cea31c36cc032339 – < b9d604933d5fd72dd37f24e1dc35f778297d745a
    • affected 2cdab4b4bf77369961f706cdeb7d040db10c5217 – < 7dd12f85f150010ef7518201c63fa7e395f5c3e9
    • affected f7d43dd206e7e18c182f200e67a8db8c209907fa – < 6881e75237a84093d0986f56223db3724619f26e
  • Linux · Linux

    • affected 6.1.103 – < 6.1.105
    • affected 6.6.44 – < 6.6.46
    • affected 6.10.3 – < 6.10.5

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-44968 badge
[![CVE-2024-44968](https://cveledger.app/badge/CVE-2024-44968.svg)](https://cveledger.app/cve/CVE-2024-44968)

Record last updated .