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-46845tracing/timerlat: Only clear timer if a kthread exists

Description

In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Only clear timer if a kthread exists The timerlat tracer can use user space threads to check for osnoise and timer latency. If the program using this is killed via a SIGTERM, the threads are shutdown one at a time and another tracing instance can start up resetting the threads before they are fully closed. That causes the hrtimer assigned to the kthread to be shutdown and freed twice when the dying thread finally closes the file descriptors, causing a use-after-free bug. Only cancel the hrtimer if the associated thread is still around. Also add the interface_lock around the resetting of the tlat_var->kthread. Note, this is just a quick fix that can be backported to stable. A real fix is to have a better synchronization between the shutdown of old threads and the starting of new ones.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 23 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-46845, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% 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: High 7.8.

Affected products

  • Linux · Linux

    • affected e88ed227f639ebcb31ed4e5b88756b47d904584b – < 8c72f0b2c45f21cb8b00fc37f79f632d7e46c2ed
    • affected e88ed227f639ebcb31ed4e5b88756b47d904584b – < 8a9d0d405159e9c796ddf771f7cff691c1a2bc1e
    • affected e88ed227f639ebcb31ed4e5b88756b47d904584b – < e6a53481da292d970d1edf0d8831121d1c5e2f0d
  • Linux · Linux

    • affected 6.5
    • unaffected < 6.5
    • unaffected 6.6.51 – ≤ 6.6.*
    • unaffected 6.10.10 – ≤ 6.10.*
    • unaffected 6.11 – ≤ *

References

References3

Sources

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

Badge for a README or a ticket

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

Record last updated .