CVE-2023-53478

MEDIUMNVD 4.74.7—
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory published 2025-10-01. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
4.7
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.7Exploit: NoneExposed: 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/synthetic: Fix races on freeing last_cmd

Currently, the "last_cmd" variable can be accessed by multiple processes asynchronously when multiple users manipulate synthetic_events node at the same time, it could lead to use-after-free or double-free.

This patch add "lastcmd_mutex" to prevent "last_cmd" from being accessed asynchronously.

================================================================

It's easy to reproduce in the KASAN environment by running the two scripts below in different shells.

script 1: while : do echo -n -e '\x88' > /sys/kernel/tracing/synthetic_events done

script 2: while : do echo -n -e '\xb0' > /sys/kernel/tracing/synthetic_events done

================================================================ double-free scenario:

process A process B ------------------- --------------- 1.kstrdup last_cmd 2.free last_cmd 3.free last_cmd(double-free)

================================================================ use-after-free scenario:

process A process B ------------------- --------------- 1.kstrdup last_cmd 2.free last_cmd 3.tracing_log_err(use-after-free)

================================================================

Appendix 1. KASAN report double-free:

BUG: KASAN: double-free in kfree+0xdc/0x1d4 Free of addr * by task sh/4879 Call trace: ... kfree+0xdc/0x1d4 create_or_delete_synth_event+0x60/0x1e8 trace_parse_run_command+0x2bc/0x4b8 synth_events_write+0x20/0x30 vfs_write+0x200/0x830 ...

Allocated by task 4879: ... kstrdup+0x5c/0x98 create_or_delete_synth_event+0x6c/0x1e8 trace_parse_run_command+0x2bc/0x4b8 synth_events_write+0x20/0x30 vfs_write+0x200/0x830 ...

Freed by task 5464: ... kfree+0xdc/0x1d4 create_or_delete_synth_event+0x60/0x1e8 trace_parse_run_command+0x2bc/0x4b8 synth_events_write+0x20/0x30 vfs_write+0x200/0x830 ...

================================================================ Appendix 2. KASAN report use-after-free:

BUG: KASAN: use-after-free in strlen+0x5c/0x7c Read of size 1 at addr * by task sh/5483 sh: CPU: 7 PID: 5483 Comm: sh ... __asan_report_load1_noabort+0x34/0x44 strlen+0x5c/0x7c tracing_log_err+0x60/0x444 create_or_delete_synth_event+0xc4/0x204 trace_parse_run_command+0x2bc/0x4b8 synth_events_write+0x20/0x30 vfs_write+0x200/0x830 ...

Allocated by task 5483: ... kstrdup+0x5c/0x98 create_or_delete_synth_event+0x80/0x204 trace_parse_run_command+0x2bc/0x4b8 synth_events_write+0x20/0x30 vfs_write+0x200/0x830 ...

Freed by task 5480: ... kfree+0xdc/0x1d4 create_or_delete_synth_event+0x74/0x204 trace_parse_run_command+0x2bc/0x4b8 synth_events_write+0x20/0x30 vfs_write+0x200/0x830 ...

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
26(Track)
EG Risk 26/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
Severity47% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
1.0%
KEV
Not listed

Published

October 1, 2025

Last Modified

January 20, 2026

References (3)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.1.24—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.

Data Freshness Timeline

(refreshed 13× in last 7d / 37× 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-07-24 14:16 UTCEPSS rescore
  2. 2026-07-23 19:11 UTCOSV refresh
  3. 2026-07-23 14:16 UTCEPSS rescore
  4. 2026-07-23 02:29 UTCEG score recompute
  5. 2026-07-22 23:16 UTCEG score recompute
  6. 2026-07-22 14:07 UTCEPSS rescore
  7. 2026-07-22 14:07 UTCEPSS rescore
  8. 2026-07-21 15:23 UTCEPSS rescore
  9. 2026-07-20 17:06 UTCEPSS rescore
  10. 2026-07-19 14:30 UTCEPSS rescore
  11. 2026-07-19 14:29 UTCEPSS rescore
  12. 2026-07-18 10:03 UTCEPSS rescore
  13. 2026-07-18 10:03 UTCEPSS rescore
  14. 2026-07-16 17:01 UTCEPSS rescore
  15. 2026-07-15 16:56 UTCEPSS rescore
  16. 2026-07-15 01:59 UTCEPSS rescore
  17. 2026-07-15 01:59 UTCEPSS rescore
  18. 2026-07-13 22:28 UTCEPSS rescore
  19. 2026-07-13 22:28 UTCEPSS rescore
  20. 2026-07-12 05:45 UTCEPSS rescore
  21. 2026-07-12 05:45 UTCEPSS rescore
  22. 2026-07-09 19:08 UTCEPSS rescore
  23. 2026-07-08 15:13 UTCEPSS rescore
  24. 2026-07-07 13:45 UTCEPSS rescore
  25. 2026-07-07 13:44 UTCEPSS rescore
Show 51 more
  1. 2026-07-06 13:11 UTCOSV refresh
  2. 2026-07-06 02:22 UTCEPSS rescore
  3. 2026-07-06 02:22 UTCEPSS rescore
  4. 2026-07-05 02:29 UTCEPSS rescore
  5. 2026-07-04 06:29 UTCEPSS rescore
  6. 2026-07-01 15:05 UTCEPSS rescore
  7. 2026-06-30 23:21 UTCEPSS rescore
  8. 2026-06-30 23:21 UTCEPSS rescore
  9. 2026-06-28 14:06 UTCEPSS rescore
  10. 2026-06-28 14:06 UTCEPSS rescore
  11. 2026-06-28 04:55 UTCEPSS rescore
  12. 2026-06-27 03:07 UTCEPSS rescore
  13. 2026-06-24 14:04 UTCEPSS rescore
  14. 2026-06-24 14:04 UTCEPSS rescore
  15. 2026-06-23 21:31 UTCEPSS rescore
  16. 2026-06-23 21:31 UTCEPSS rescore
  17. 2026-06-22 14:24 UTCEPSS rescore
  18. 2026-06-22 14:24 UTCEPSS rescore
  19. 2026-06-21 01:58 UTCEPSS rescore
  20. 2026-06-21 01:58 UTCEPSS rescore
  21. 2026-06-19 19:24 UTCEPSS rescore
  22. 2026-06-19 19:24 UTCEPSS rescore
  23. 2026-06-18 01:35 UTCOSV refresh
  24. 2026-06-17 17:51 UTCEPSS rescore
  25. 2026-06-15 17:47 UTCEPSS rescore
  26. 2026-06-14 23:16 UTCEPSS rescore
  27. 2026-06-13 22:59 UTCEPSS rescore
  28. 2026-06-13 22:59 UTCEPSS rescore
  29. 2026-06-12 23:11 UTCEPSS rescore
  30. 2026-06-11 13:59 UTCEPSS rescore
  31. 2026-06-10 22:17 UTCEPSS rescore
  32. 2026-06-08 14:16 UTCEPSS rescore
  33. 2026-06-08 14:16 UTCEPSS rescore
  34. 2026-06-07 15:24 UTCEPSS rescore
  35. 2026-06-07 15:24 UTCEPSS rescore
  36. 2026-06-06 13:46 UTCEPSS rescore
  37. 2026-06-06 13:46 UTCEPSS rescore
  38. 2026-06-05 22:46 UTCEPSS rescore
  39. 2026-06-05 22:46 UTCEPSS rescore
  40. 2026-06-05 06:09 UTCEPSS rescore
  41. 2026-06-05 06:09 UTCEPSS rescore
  42. 2026-06-04 13:11 UTCEPSS rescore
  43. 2026-06-04 13:11 UTCEPSS rescore
  44. 2026-06-02 20:12 UTCEPSS rescore
  45. 2026-06-02 20:12 UTCEPSS rescore
  46. 2026-06-01 13:51 UTCEPSS rescore
  47. 2026-05-31 00:15 UTCEPSS rescore
  48. 2026-05-31 00:15 UTCEPSS rescore
  49. 2026-05-29 21:46 UTCEG score recompute
  50. 2026-05-29 21:45 UTCGHSA enrichment
  51. 2026-05-29 13:43 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2023-53478?
CVE-2023-53478 is a medium vulnerability published on October 1, 2025. In the Linux kernel, the following vulnerability has been resolved: tracing/synthetic: Fix races on freeing last_cmd Currently, the "last_cmd" variable can be accessed by multiple processes asynchronously when multiple users manipulate synthetic_events node at the same time, it could lead to…
When was CVE-2023-53478 disclosed?
CVE-2023-53478 was first published in the National Vulnerability Database on October 1, 2025, with the most recent update on January 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-53478 actively exploited?
CVE-2023-53478 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-53478?
CVE-2023-53478 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2023-53478?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-53478, 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-2023-53478

Explore →

Is Your Infrastructure Affected by CVE-2023-53478?

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

Start Free Scan →Browse All CVEs