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-42096x86: stop playing stack games in profile_pc()

Description

In the Linux kernel, the following vulnerability has been resolved: x86: stop playing stack games in profile_pc() The 'profile_pc()' function is used for timer-based profiling, which isn't really all that relevant any more to begin with, but it also ends up making assumptions based on the stack layout that aren't necessarily valid. Basically, the code tries to account the time spent in spinlocks to the caller rather than the spinlock, and while I support that as a concept, it's not worth the code complexity or the KASAN warnings when no serious profiling is done using timers anyway these days. And the code really does depend on stack layout that is only true in the simplest of cases. We've lost the comment at some point (I think when the 32-bit and 64-bit code was unified), but it used to say: Assume the lock function has either no stack frame or a copy of eflags from PUSHF. which explains why it just blindly loads a word or two straight off the stack pointer and then takes a minimal look at the values to just check if they might be eflags or the return pc: Eflags always has bits 22 and up cleared unlike kernel addresses but that basic stack layout assumption assumes that there isn't any lock debugging etc going on that would complicate the code and cause a stack frame. It causes KASAN unhappiness reported for years by syzkaller [1] and others [2]. With no real practical reason for this any more, just remove the code. Just for historical interest, here's some background commits relating to this code from 2006: 0cb91a229364 ("i386: Account spinlocks to the caller during profiling for !FP kernels") 31679f38d886 ("Simplify profile_pc on x86-64") and a code unification from 2009: ef4512882dbe ("x86: time_32/64.c unify profile_pc") but the basics of this thing actually goes back to before the git tree.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 years 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-42096, 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.24% · top 85% of all CVEs (18 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 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 65ebdde16e7f5da99dbf8a548fb635837d78384e
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 27c3be840911b15a3f24ed623f86153c825b6b29
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 49c09ca35a5f521d7fa18caf62fdf378f15e8aa4
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2d07fea561d64357fb7b3f3751e653bf20306d77
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 161cef818545ecf980f0e2ebaf8ba7326ce53c2b
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 16222beb9f8e5ceb0beeb5cbe54bef16df501a92
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a3b65c8cbc139bfce9541bc81c1bb766e5ba3f68
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 093d9603b60093a9aaae942db56107f6432a5dca
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 4.19.317 – ≤ 4.19.*
    • unaffected 5.4.279 – ≤ 5.4.*
    • unaffected 5.10.221 – ≤ 5.10.*
    • unaffected 5.15.162 – ≤ 5.15.*
    • unaffected 6.1.97 – ≤ 6.1.*
    • unaffected 6.6.37 – ≤ 6.6.*
    • unaffected 6.9.8 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References11

Sources

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

Badge for a README or a ticket

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

Record last updated .