CVE-2026-74471

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

tracing: Check return value of __register_event() in trace_module_add_events()

trace_module_add_events() ignores the return value of __register_event() and unconditionally calls __add_event_to_tracers() for each event.

If __register_event() fails (for example, if event_init() fails), the trace_event_call is not added to ftrace_events list, but __add_event_to_tracers() still creates a trace_event_file pointing to it. If module loading subsequently fails and module memory is freed, tracing state retains a stale trace_event_call pointer in trace_event_file, leading to a use-after-free when tracefs or tracing subsystem operations are later executed.

Fix this by checking the return value of __register_event() and only calling __add_event_to_tracers() if event registration succeeded.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 19, 2026

Advisory Details (5)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

tracing: Check return value of __register_event() in trace_module_add_events() - kernel/git/stable/linux.git - Linux kernel stable tree

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

tracing: Check return value of __register_event() in trace_module_add_events() - kernel/git/stable/linux.git - Linux kernel stable tree

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

tracing: Check return value of __register_event() in trace_module_add_events() - kernel/git/stable/linux.git - Linux kernel stable tree

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

tracing: Check return value of __register_event() in trace_module_add_events() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/22f954f7a8afe975e85517aff41b35defe05144b
generic

tracing: Check return value of __register_event() in trace_module_add_events() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/000765dcdc3edf128990762790543adc4b868f6c

Vendor Advisories for CVE-2026-74471(1)

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

Data Freshness Timeline

(refreshed 31× in last 7d / 31× 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-08-21 03:47 UTCEG score recompute
  2. 2026-08-21 03:47 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 16:24 UTCGHSA enrichment
  5. 2026-08-20 05:00 UTCGHSA enrichment
  6. 2026-08-19 17:36 UTCEG score recompute
  7. 2026-08-19 17:36 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 16:41 UTCGHSA enrichment
  10. 2026-08-19 05:16 UTCGHSA enrichment
  11. 2026-08-18 17:49 UTCEG score recompute
  12. 2026-08-18 17:49 UTCGHSA enrichment
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 13:49 UTCEPSS rescore
  15. 2026-08-18 06:18 UTCGHSA enrichment
  16. 2026-08-17 18:55 UTCEG score recompute
  17. 2026-08-17 18:55 UTCGHSA enrichment
  18. 2026-08-17 13:47 UTCEPSS rescore
  19. 2026-08-17 06:25 UTCEG score recompute
  20. 2026-08-17 06:25 UTCGHSA enrichment
  21. 2026-08-17 05:55 UTCEG score recompute▲ 7.80
  22. 2026-08-17 05:55 UTCGHSA enrichment
  23. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  24. 2026-08-17 05:25 UTCEG score recompute
  25. 2026-08-17 05:25 UTCGHSA enrichment
Show 6 more
  1. 2026-08-17 05:24 UTCMITRE cvelistV5
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-15 13:27 UTCNVD update
  5. 2026-08-15 12:40 UTCEG score recompute
  6. 2026-08-15 12:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74471?
CVE-2026-74471 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: tracing: Check return value of registerevent() in tracemoduleaddevents() tracemoduleaddevents() ignores the return value of registerevent() and unconditionally calls addeventto_tracers() for each event. If registerevent() fails…
When was CVE-2026-74471 disclosed?
CVE-2026-74471 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74471 actively exploited?
CVE-2026-74471 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 97.4% of all scored CVEs.
What is the CVSS score of CVE-2026-74471?
CVE-2026-74471 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-74471?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74471, 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-2026-74471

Explore →

Is Your Infrastructure Affected by CVE-2026-74471?

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

Start Free Scan →Browse All CVEs