CVE-2024-46788

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.5 from GitHub Security Advisory published 2024-09-18. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2024-42049 (ENISA EUVD) · GHSA-3h89-g9r5-cvx9 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

tracing/osnoise: Use a cpumask to know what threads are kthreads

The start_kthread() and stop_thread() code was not always called with the interface_lock held. This means that the kthread variable could be unexpectedly changed causing the kthread_stop() to be called on it when it should not have been, leading to:

while true; do rtla timerlat top -u -q & PID=$!; sleep 5; kill -INT $PID; sleep 0.001; kill -TERM $PID; wait $PID; done

Causing the following OOPS:

Oops: general protection fault, probably for non-canonical address 0xdffffc0000000002: 0000 [#1] PREEMPT SMP KASAN PTI KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017] CPU: 5 UID: 0 PID: 885 Comm: timerlatu/5 Not tainted 6.11.0-rc4-test-00002-gbc754cc76d1b-dirty #125 a533010b71dab205ad2f507188ce8c82203b0254 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:hrtimer_active+0x58/0x300 Code: 48 c1 ee 03 41 54 48 01 d1 48 01 d6 55 53 48 83 ec 20 80 39 00 0f 85 30 02 00 00 49 8b 6f 30 4c 8d 75 10 4c 89 f0 48 c1 e8 03 <0f> b6 3c 10 4c 89 f0 83 e0 07 83 c0 03 40 38 f8 7c 09 40 84 ff 0f RSP: 0018:ffff88811d97f940 EFLAGS: 00010202 RAX: 0000000000000002 RBX: ffff88823c6b5b28 RCX: ffffed10478d6b6b RDX: dffffc0000000000 RSI: ffffed10478d6b6c RDI: ffff88823c6b5b28 RBP: 0000000000000000 R08: ffff88823c6b5b58 R09: ffff88823c6b5b60 R10: ffff88811d97f957 R11: 0000000000000010 R12: 00000000000a801d R13: ffff88810d8b35d8 R14: 0000000000000010 R15: ffff88823c6b5b28 FS: 0000000000000000(0000) GS:ffff88823c680000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000561858ad7258 CR3: 000000007729e001 CR4: 0000000000170ef0 Call Trace: ? die_addr+0x40/0xa0 ? exc_general_protection+0x154/0x230 ? asm_exc_general_protection+0x26/0x30 ? hrtimer_active+0x58/0x300 ? __pfx_mutex_lock+0x10/0x10 ? __pfx_locks_remove_file+0x10/0x10 hrtimer_cancel+0x15/0x40 timerlat_fd_release+0x8e/0x1f0 ? security_file_release+0x43/0x80 __fput+0x372/0xb10 task_work_run+0x11e/0x1f0 ? _raw_spin_lock+0x85/0xe0 ? __pfx_task_work_run+0x10/0x10 ? poison_slab_object+0x109/0x170 ? do_exit+0x7a0/0x24b0 do_exit+0x7bd/0x24b0 ? __pfx_migrate_enable+0x10/0x10 ? __pfx_do_exit+0x10/0x10 ? __pfx_read_tsc+0x10/0x10 ? ktime_get+0x64/0x140 ? _raw_spin_lock_irq+0x86/0xe0 do_group_exit+0xb0/0x220 get_signal+0x17ba/0x1b50 ? vfs_read+0x179/0xa40 ? timerlat_fd_read+0x30b/0x9d0 ? __pfx_get_signal+0x10/0x10 ? __pfx_timerlat_fd_read+0x10/0x10 arch_do_signal_or_restart+0x8c/0x570 ? __pfx_arch_do_signal_or_restart+0x10/0x10 ? vfs_read+0x179/0xa40 ? ksys_read+0xfe/0x1d0 ? __pfx_ksys_read+0x10/0x10 syscall_exit_to_user_mode+0xbc/0x130 do_syscall_64+0x74/0x110 ? __pfx___rseq_handle_notify_resume+0x10/0x10 ? __pfx_ksys_read+0x10/0x10 ? fpregs_restore_userregs+0xdb/0x1e0 ? fpregs_restore_userregs+0xdb/0x1e0 ? syscall_exit_to_user_mode+0x116/0x130 ? do_syscall_64+0x74/0x110 ? do_syscall_64+0x74/0x110 ? do_syscall_64+0x74/0x110 entry_SYSCALL_64_after_hwframe+0x71/0x79 RIP: 0033:0x7ff0070eca9c Code: Unable to access opcode bytes at 0x7ff0070eca72. RSP: 002b:00007ff006dff8c0 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 RAX: 0000000000000000 RBX: 0000000000000005 RCX: 00007ff0070eca9c RDX: 0000000000000400 RSI: 00007ff006dff9a0 RDI: 0000000000000003 RBP: 00007ff006dffde0 R08: 0000000000000000 R09: 00007ff000000ba0 R10: 00007ff007004b08 R11: 0000000000000246 R12: 0000000000000003 R13: 00007ff006dff9a0 R14: 0000000000000007 R15: 0000000000000008 Modules linked in: snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hwdep snd_hda_core ---[ end trace 0000000000000000 ]---

This is because it would mistakenly call kthread_stop() on a user space thread making it "exit" before it actually exits.

Since kthread ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
11th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 18, 2024

Last Modified

August 5, 2026

References (3)

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-gkeop-6.8 (6.8.0-1002.4) @ noble2026-10-24ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1019.21.1) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-50.51~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-azure (6.8.0-1020.23) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-24.04 (6.8.0-50.51) @ noble2026-10-24ubuntu
linuxKernel @ 6.6.51 (fixes >=6.5.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.10.11-1: fixed in 6.10.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.10.11-1: fixed in 6.10.11-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 209 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 113 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:41 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  2. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  4. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  5. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  6. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  7. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  8. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  9. 2026-10-25 17:01 UTCEG score recompute
  10. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  11. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  12. 2026-10-24 04:36 UTCEG score recompute
  13. 2026-10-24 04:36 UTCVendor advisory
  14. 2026-10-24 04:36 UTCGHSA enrichmentGHSA-3h89-g9r5-cvx9 · GitHub CVSS 5.5
  15. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  16. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  17. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  18. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  19. 2026-10-19 18:25 UTCOSV refresh
  20. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  21. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  22. 2026-10-18 06:58 UTCEG score recompute
  23. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  24. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  25. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
Show 71 more
  1. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-10-12 17:44 UTCEG score recompute
  4. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-10-11 21:09 UTCEG score recompute
  6. 2026-10-11 16:01 UTCEG score recompute
  7. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-09-30 19:54 UTCEG score recompute
  18. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  22. 2026-09-26 23:12 UTCOSV refresh
  23. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  24. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  25. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  26. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  27. 2026-09-21 20:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  28. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  29. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  30. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  31. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  32. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  33. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  34. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  35. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  36. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  37. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  38. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  39. 2026-09-07 08:48 UTCOSV refresh
  40. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  41. 2026-09-05 15:27 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  42. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  43. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  44. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  45. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  46. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  47. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  48. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  49. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  50. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  51. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  52. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  53. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  54. 2026-08-20 18:31 UTCOSV refresh
  55. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  56. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  57. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  58. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  59. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  60. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  61. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  62. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  63. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  64. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  65. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  66. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  67. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  68. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  69. 2026-08-05 12:00 UTCEG score recompute
  70. 2026-08-05 12:00 UTCVendor advisory
  71. 2026-08-05 12:00 UTCGHSA enrichmentGHSA-3h89-g9r5-cvx9 · GitHub CVSS 5.5

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-46788?
CVE-2024-46788 is a medium-severity vulnerability; its CVE record was published on September 18, 2024. In the Linux kernel, the following vulnerability has been resolved: tracing/osnoise: Use a cpumask to know what threads are kthreads The start_kthread() and stop_thread() code was not always called with the interface_lock held. This means that the kthread variable could be unexpectedly changed…
When was the CVE record for CVE-2024-46788 published?
The CVE record for CVE-2024-46788 was published on September 18, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2024-46788 actively exploited?
CVE-2024-46788 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-46788?
CVE-2024-46788 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-46788?
A fix for CVE-2024-46788 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-46788

Explore →

Is Your Infrastructure Affected by CVE-2024-46788?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs