CVE-2026-64451

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-25. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
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: Fix NULL pointer dereference in func_set_flag()

func_set_flag() dereferences tr->current_trace_flags before verifying that the current tracer is actually the function tracer. When the active tracer has been switched away from "function" (e.g., to "wakeup_rt"), tr->current_trace_flags can be NULL, leading to a NULL pointer dereference and kernel crash.

The call chain that triggers this is:

trace_options_write() -> __set_tracer_option() -> trace->set_flag() /* func_set_flag */

In func_set_flag(), the first operation is:

if (!!set == !!(tr->current_trace_flags->val & bit))

This dereferences tr->current_trace_flags unconditionally. The safety check that guards against a non-function tracer:

if (tr->current_trace != &function_trace) return 0;

is placed *after* the dereference, which is too late.

This was observed with the following crash dump:

BUG: unable to handle page fault at 0000000000000000 RIP: func_set_flag+0xd

Call Trace: __set_tracer_option+0x27 trace_options_write+0x75 vfs_write+0x12a ksys_write+0x66 do_syscall_64+0x5b

RIP: ffffffff914c973d RSP: ff67ec88b01dfdf0 RFLAGS: 00010202 RAX: 0000000000000000 RBX: ff3a826e80354580 RCX: 0000000000000001 RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffffffff93918080

The disassembly confirms the fault:

func_set_flag+0: mov 0x1f08(%rdi), %rax ; RAX = tr->current_trace_flags = NULL func_set_flag+13: mov (%rax), %eax ; page fault: dereference NULL

At the time of the crash: tr->current_trace_flags = 0x0 (NULL) tr->current_trace = wakeup_rt_tracer (not function_trace)

The scenario is that a process opens a function tracer option file (such as "func_stack_trace"), then the current tracer is switched to another tracer (e.g., "wakeup_rt"), which sets current_trace_flags to NULL. When the process subsequently writes to the option file, func_set_flag() is invoked and crashes on the NULL dereference.

Fix this by moving the current_trace check before the current_trace_flags dereference, so that func_set_flag() returns early when the function tracer is not active.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 25, 2026

Last Modified

September 3, 2026

Advisory Details (2)

Auto-updated Sep 3, 2026
No patch confirmed yet.
generic

tracing: Fix NULL pointer dereference in func_set_flag() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c3e94604675e3db186111b8942650d86577df9b0
generic

tracing: Fix NULL pointer dereference in func_set_flag() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/69f17ac132a38974cf1defb480cef6b79d1ab768

Vendor Advisories for CVE-2026-64451(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-15ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-15ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-15ubuntu

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (158 versions)7.1.4-1

Weakness Classification(1)

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

All Vendor Advisories

(3)

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 20× in last 7d / 61× 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.

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

Frequently asked(5)

What is CVE-2026-64451?
CVE-2026-64451 is a medium vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: tracing: Fix NULL pointer dereference in funcsetflag() funcsetflag() dereferences tr->currenttraceflags before verifying that the current tracer is actually the function tracer. When the active tracer has been switched away from…
When was CVE-2026-64451 disclosed?
CVE-2026-64451 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64451 actively exploited?
CVE-2026-64451 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 98.5% of all scored CVEs.
What is the CVSS score of CVE-2026-64451?
CVE-2026-64451 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64451?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64451, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64451

Explore →

Is Your Infrastructure Affected by CVE-2026-64451?

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