Skip to content
Fencer Vulns
high 7.8

CVE-2024-46845 json

tracing/timerlat: Only clear timer if a kthread exists

published 2024-09-27 2 y ago modified 2026-08-05 3 mo ago also EUVD-2024-42106

cvss
7.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 14%
public exploits
0
none known

Summary

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.

Patch / fix

  • Linux Linux 6.6.51, 6.10.10, 6.11
  • linux Debian 14, Debian 13 6.10.11-1

debian advisories DEBIAN-CVE-2024-46845

  • linux Ubuntu 24.04 LTS 6.8.0-50.51
  • linux-aws Ubuntu 24.04 LTS 6.8.0-1020.22
  • linux-gcp Ubuntu 24.04 LTS 6.8.0-1019.21
  • linux-gke Ubuntu 24.04 LTS 6.8.0-1015.19
  • linux-ibm Ubuntu 24.04 LTS 6.8.0-1017.17
  • linux-azure Ubuntu 24.04 LTS 6.8.0-1020.23
  • linux-gkeop Ubuntu 24.04 LTS 6.8.0-1002.4
  • linux-raspi Ubuntu 24.04 LTS 6.8.0-1016.18

ubuntu advisories UBUNTU-CVE-2024-46845

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-source Linux Micro 6.1, Linux Micro 6.0 6.4.0-24.1
  • kernel-default Linux Micro 6.1, Linux Micro 6.0 6.4.0-24.1
  • kernel-kvmsmall Linux Micro 6.1, Linux Micro 6.0 6.4.0-24.1
  • kernel-default-base Linux Micro 6.1, Linux Micro 6.0 6.4.0-24.1.21.4
  • kernel-livepatch-MICRO-6-0_Update_4 Linux Micro 6.1, Linux Micro 6.0 1-1.2
  • kernel-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-22.1
  • kernel-source-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-22.1
  • kernel-livepatch-MICRO-6-0-RT_Update_4 Linux Micro 6.1, Linux Micro 6.0 1-1.1

suse advisories SUSE-SU-2025:20164-1SUSE-SU-2025:20247-1SUSE-SU-2025:20163-1SUSE-SU-2025:20246-1SUSE-SU-2024:4387-1SUSE-SU-2024:4318-1

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-46845 updated cvss 4.1

kernel: tracing/timerlat: Only clear timer if a kthread exists

  • Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    affected: workaround, no fix available
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more
    not 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.24% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Linux Linux

Classification

Weakness
Technology feeds

References

Sources

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.