LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53793: perf tool x86: Fix perf_env memory leak

In the Linux kernel, the following vulnerability has been resolved: perf tool x86: Fix perf_env memory leak Found by leak sanitizer: ``` ==1632594==ERROR: LeakSanitizer: detected memory leaks Direct leak of 21 byte(s) in 1 object(s) allocated from: #0 0x7f2953a7077b in __interceptor_strdup ../../../../src/libsanitizer/asan/asan_interceptors.cpp:439 #1 0x556701d6fbbf in perf_env__read_cpuid util/env.c:369 #2 0x556701d70589 in perf_env__cpuid util/env.c:465 #3 0x55670204bba2 in x86__is_amd_cpu arch/x86/util/env.c:14 #4 0x5567020487a2 in arch__post_evsel_config arch/x86/util/evsel.c:83 #5 0x556701d8f78b in evsel__config util/evsel.c:1366 #6 0x556701ef5872 in evlist__config util/record.c:108 #7 0x556701cd6bcd in test__PERF_RECORD tests/perf-record.c:112 #8 0x556701cacd07 in run_test tests/builtin-test.c:236 #9 0x556701cacfac in test_and_print tests/builtin-test.c:265 #10 0x556701cadddb in __cmd_test tests/builtin-test.c:402 #11 0x556701caf2aa in cmd_test tests/builtin-test.c:559 #12 0x556701d3b557 in run_builtin tools/perf/perf.c:323 #13 0x556701d3bac8 in handle_internal_command tools/perf/perf.c:377 #14 0x556701d3be90 in run_argv tools/perf/perf.c:421 #15 0x556701d3c3f8 in main tools/perf/perf.c:537 #16 0x7f2952a46189 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58 SUMMARY: AddressSanitizer: 21 byte(s) leaked in 1 allocation(s). ```

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This CVE describes a memory leak in the Linux kernel perf tool on x86. The provided evidence shows a small leak found by LeakSanitizer during perf testing, not a remote compromise path. Business urgency appears low unless affected perf builds are widely used in sensitive operational environments.

Executive priority

Treat as routine patch management. No source evidence indicates active exploitation or severe business impact, but affected Linux packages should be updated through normal maintenance windows.

Technical view

The issue is in perf_env CPU ID handling used by x86 perf configuration paths. A strdup allocation from perf_env__read_cpuid was not freed, producing a 21-byte leak in sanitizer output. The source bundle lists Linux 6.1 through 6.5-related affected versions and stable kernel fixes.

Likely exposure

Exposure is most likely on Linux systems using affected kernel/perf tool builds on x86. The bundle names Linux versions around 6.1, 6.1.39, 6.3.13, 6.4.4, and 6.5, but distribution package mapping is not provided.

Exploitation context

The provided sources do not show active exploitation, KEV listing, exploit availability, CVSS scoring, or a privilege escalation path. Evidence supports a memory leak fixed in perf, discovered through sanitizer testing.

Researcher notes

The public bundle lacks CVSS, CWE, exploit notes, and distro-specific affected package data. Analysis should stay limited to the perf_env memory leak and the referenced upstream stable fixes.

Mitigation direction

  • Check Linux vendor or distribution advisories for CVE-2023-53793 mapping.
  • Update kernel/perf packages to versions containing the referenced stable fixes.
  • Prioritize systems where perf is installed or used for diagnostics.
  • Track CVE and vendor pages for severity or scope updates.

Validation and detection

  • Inventory Linux kernel and perf package versions across x86 systems.
  • Confirm installed packages include one of the referenced stable fixes.
  • Review vulnerability scanner findings against vendor package advisories.
  • Document exceptions where perf is absent or not distributed.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-53793 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf7b58cbdb3ff36eba8622e67eee66c10dd1c9995, f7b58cbdb3ff36eba8622e67eee66c10dd1c9995, f7b58cbdb3ff36eba8622e67eee66c10dd1c9995, f7b58cbdb3ff36eba8622e67eee66c10dd1c9995unaffected
LinuxLinux6.1, 0, 6.1.39, 6.3.13, 6.4.4, 6.5affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.