CVE-2024-26703

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

tracing/timerlat: Move hrtimer_init to timerlat_fd open()

Currently, the timerlat's hrtimer is initialized at the first read of timerlat_fd, and destroyed at close(). It works, but it causes an error if the user program open() and close() the file without reading.

Here's an example:

# echo NO_OSNOISE_WORKLOAD > /sys/kernel/debug/tracing/osnoise/options # echo timerlat > /sys/kernel/debug/tracing/current_tracer

# cat < ./timerlat_load.py # !/usr/bin/env python3

timerlat_fd = open("/sys/kernel/tracing/osnoise/per_cpu/cpu0/timerlat_fd", 'r') timerlat_fd.close(); EOF

# ./taskset -c 0 ./timerlat_load.py

BUG: kernel NULL pointer dereference, address: 0000000000000010 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 1 PID: 2673 Comm: python3 Not tainted 6.6.13-200.fc39.x86_64 #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-1.fc39 04/01/2014 RIP: 0010:hrtimer_active+0xd/0x50 Code: 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 48 8b 57 30 <8b> 42 10 a8 01 74 09 f3 90 8b 42 10 a8 01 75 f7 80 7f 38 00 75 1d RSP: 0018:ffffb031009b7e10 EFLAGS: 00010286 RAX: 000000000002db00 RBX: ffff9118f786db08 RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffff9117a0e64400 RDI: ffff9118f786db08 RBP: ffff9118f786db80 R08: ffff9117a0ddd420 R09: ffff9117804d4f70 R10: 0000000000000000 R11: 0000000000000000 R12: ffff9118f786db08 R13: ffff91178fdd5e20 R14: ffff9117840978c0 R15: 0000000000000000 FS: 00007f2ffbab1740(0000) GS:ffff9118f7840000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000010 CR3: 00000001b402e000 CR4: 0000000000750ee0 PKRU: 55555554 Call Trace: ? __die+0x23/0x70 ? page_fault_oops+0x171/0x4e0 ? srso_alias_return_thunk+0x5/0x7f ? avc_has_extended_perms+0x237/0x520 ? exc_page_fault+0x7f/0x180 ? asm_exc_page_fault+0x26/0x30 ? hrtimer_active+0xd/0x50 hrtimer_cancel+0x15/0x40 timerlat_fd_release+0x48/0xe0 __fput+0xf5/0x290 __x64_sys_close+0x3d/0x80 do_syscall_64+0x60/0x90 ? srso_alias_return_thunk+0x5/0x7f ? __x64_sys_ioctl+0x72/0xd0 ? srso_alias_return_thunk+0x5/0x7f ? syscall_exit_to_user_mode+0x2b/0x40 ? srso_alias_return_thunk+0x5/0x7f ? do_syscall_64+0x6c/0x90 ? srso_alias_return_thunk+0x5/0x7f ? exit_to_user_mode_prepare+0x142/0x1f0 ? srso_alias_return_thunk+0x5/0x7f ? syscall_exit_to_user_mode+0x2b/0x40 ? srso_alias_return_thunk+0x5/0x7f ? do_syscall_64+0x6c/0x90 entry_SYSCALL_64_after_hwframe+0x6e/0xd8 RIP: 0033:0x7f2ffb321594 Code: 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 80 3d d5 cd 0d 00 00 74 13 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 3c c3 0f 1f 00 55 48 89 e5 48 83 ec 10 89 7d RSP: 002b:00007ffe8d8eef18 EFLAGS: 00000202 ORIG_RAX: 0000000000000003 RAX: ffffffffffffffda RBX: 00007f2ffba4e668 RCX: 00007f2ffb321594 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003 RBP: 00007ffe8d8eef40 R08: 0000000000000000 R09: 0000000000000000 R10: 55c926e3167eae79 R11: 0000000000000202 R12: 0000000000000003 R13: 00007ffe8d8ef030 R14: 0000000000000000 R15: 00007f2ffba4e668 CR2: 0000000000000010 ---[ end trace 0000000000000000 ]---

Move hrtimer_init to timerlat_fd open() to avoid this problem.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

April 3, 2024

Last Modified

February 27, 2025

References (6)

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oem-22.04d (6.5.0.1027.29) @ jammy2026-05-24ubuntu
ubuntulinux-virtual-hwe-22.04 (6.5.0.44.44~22.04.1) @ jammy2026-05-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.5.0.44.44) @ mantic2026-05-24ubuntu
ubuntulinux-tools-gcp (6.5.0.1024.26~22.04.1) @ jammy2026-05-24ubuntu
ubuntulinux-tools-starfive (6.5.0.1017.18~22.04.1) @ jammy2026-05-24ubuntu
linuxKernel @ 6.6.18—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.

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 9× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 108 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-26703?
CVE-2024-26703 is a medium vulnerability published on April 3, 2024. In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Move hrtimerinit to timerlatfd open() Currently, the timerlat's hrtimer is initialized at the first read of timerlat_fd, and destroyed at close(). It works, but it causes an error if the user program open() and…
When was CVE-2024-26703 disclosed?
CVE-2024-26703 was first published in the National Vulnerability Database on April 3, 2024, with the most recent update on February 27, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-26703 actively exploited?
CVE-2024-26703 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 86.7% of all scored CVEs.
What is the CVSS score of CVE-2024-26703?
CVE-2024-26703 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-26703?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-26703, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-26703

Explore →

Is Your Infrastructure Affected by CVE-2024-26703?

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

Start Free Scan →Browse All CVEs