CVE-2023-53649

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 2025-10-07. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
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:

perf trace: Really free the evsel->priv area

In 3cb4d5e00e037c70 ("perf trace: Free syscall tp fields in evsel->priv") it only was freeing if strcmp(evsel->tp_format->system, "syscalls") returned zero, while the corresponding initialization of evsel->priv was being performed if it was _not_ zero, i.e. if the tp system wasn't 'syscalls'.

Just stop looking for that and free it if evsel->priv was set, which should be equivalent.

Also use the pre-existing evsel_trace__delete() function.

This resolves these leaks, detected with:

$ make EXTRA_CFLAGS="-fsanitize=address" BUILD_BPF_SKEL=1 CORESIGHT=1 O=/tmp/build/perf-tools-next -C tools/perf install-bin

================================================================= ==481565==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 40 byte(s) in 1 object(s) allocated from: #0 0x7f7343cba097 in calloc (/lib64/libasan.so.8+0xba097) #1 0x987966 in zalloc (/home/acme/bin/perf+0x987966) #2 0x52f9b9 in evsel_trace__new /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:307 #3 0x52f9b9 in evsel__syscall_tp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:333 #4 0x52f9b9 in evsel__init_raw_syscall_tp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:458 #5 0x52f9b9 in perf_evsel__raw_syscall_newtp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:480 #6 0x540e8b in trace__add_syscall_newtp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:3212 #7 0x540e8b in trace__run /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:3891 #8 0x540e8b in cmd_trace /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:5156 #9 0x5ef262 in run_builtin /home/acme/git/perf-tools-next/tools/perf/perf.c:323 #10 0x4196da in handle_internal_command /home/acme/git/perf-tools-next/tools/perf/perf.c:377 #11 0x4196da in run_argv /home/acme/git/perf-tools-next/tools/perf/perf.c:421 #12 0x4196da in main /home/acme/git/perf-tools-next/tools/perf/perf.c:537 #13 0x7f7342c4a50f in __libc_start_call_main (/lib64/libc.so.6+0x2750f)

Direct leak of 40 byte(s) in 1 object(s) allocated from: #0 0x7f7343cba097 in calloc (/lib64/libasan.so.8+0xba097) #1 0x987966 in zalloc (/home/acme/bin/perf+0x987966) #2 0x52f9b9 in evsel_trace__new /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:307 #3 0x52f9b9 in evsel__syscall_tp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:333 #4 0x52f9b9 in evsel__init_raw_syscall_tp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:458 #5 0x52f9b9 in perf_evsel__raw_syscall_newtp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:480 #6 0x540dd1 in trace__add_syscall_newtp /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:3205 #7 0x540dd1 in trace__run /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:3891 #8 0x540dd1 in cmd_trace /home/acme/git/perf-tools-next/tools/perf/builtin-trace.c:5156 #9 0x5ef262 in run_builtin /home/acme/git/perf-tools-next/tools/perf/perf.c:323 #10 0x4196da in handle_internal_command /home/acme/git/perf-tools-next/tools/perf/perf.c:377 #11 0x4196da in run_argv /home/acme/git/perf-tools-next/tools/perf/perf.c:421 #12 0x4196da in main /home/acme/git/perf-tools-next/tools/perf/perf.c:537 #13 0x7f7342c4a50f in __libc_start_call_main (/lib64/libc.so.6+0x2750f)

SUMMARY: AddressSanitizer: 80 byte(s) leaked in 2 allocation(s). [root@quaco ~]#

With this we plug all leaks with "perf trace sleep 1".

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 BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
8th
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-17). 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

October 7, 2025

Last Modified

February 3, 2026

References (4)

Vendor Advisories for CVE-2023-53649(2)

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 / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-427.13.1.el9_42024-04-30redhat
redhatkernel-0:4.18.0-372.9.1.el82022-05-10redhat
linuxKernel @ 5.15.132 (fixes >=5.14.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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.55-1~bpo11+1 (10 versions)
  • every version up to 6.1.55-1: fixed in 6.1.55-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.5.6-1: fixed in 6.5.6-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.5.6-1: fixed in 6.5.6-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 30× 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 90 of 176 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. 10 repeat rows among the latest 100 are merged into the row they repeat. The 86 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-53649?
CVE-2023-53649 is a medium-severity vulnerability; its CVE record was published on October 7, 2025. In the Linux kernel, the following vulnerability has been resolved: perf trace: Really free the evsel->priv area In 3cb4d5e00e037c70 ("perf trace: Free syscall tp fields in evsel->priv") it only was freeing if strcmp(evsel->tp_format->system, "syscalls") returned zero, while the corresponding…
When was the CVE record for CVE-2023-53649 published?
The CVE record for CVE-2023-53649 was published on October 7, 2025. 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 February 3, 2026; the record at its source may have been updated since.
Is CVE-2023-53649 actively exploited?
CVE-2023-53649 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53649?
CVE-2023-53649 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-53649?
A fix for CVE-2023-53649 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-53649 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-53649

Explore →

Is Your Infrastructure Affected by CVE-2023-53649?

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

Book a Demo →Browse All CVEs