{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-53793 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-53793 is a memory corruption vulnerability in Linux, published on 9 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-53793 and fix it if it is affected.\n\nWhat it is: CVE-2023-53793 is a memory corruption vulnerability in Linux, published on 9 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-53793 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-53793/ (Markdown: https://insights.sbomify.com/CVE-2023-53793/index.md)","id":"CVE-2023-53793","markdown":"https://insights.sbomify.com/CVE-2023-53793/index.md","name":"CVE-2023-53793","record":{"aliases":["BELL-CVE-2023-53793","DEBIAN-CVE-2023-53793","GHSA-47vm-9f65-qwhr","UBUNTU-CVE-2023-53793"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel perf tool","requires_auth":"none","summary":"A memory leak in the Linux kernel perf tool can lead to resource exhaustion and denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nperf tool x86: Fix perf_env memory leak\n\nFound by leak sanitizer:\n```\n==1632594==ERROR: LeakSanitizer: detected memory leaks\n\nDirect leak of 21 byte(s) in 1 object(s) allocated from:\n    #0 0x7f2953a7077b in __interceptor_strdup ../../../../src/libsanitizer/asan/asan_interceptors.cpp:439\n    #1 0x556701d6fbbf in perf_env__read_cpuid util/env.c:369\n    #2 0x556701d70589 in perf_env__cpuid util/env.c:465\n    #3 0x55670204bba2 in x86__is_amd_cpu arch/x86/util/env.c:14\n    #4 0x5567020487a2 in arch__post_evsel_config arch/x86/util/evsel.c:83\n    #5 0x556701d8f78b in evsel__config util/evsel.c:1366\n    #6 0x556701ef5872 in evlist__config util/record.c:108\n    #7 0x556701cd6bcd in test__PERF_RECORD tests/perf-record.c:112\n    #8 0x556701cacd07 in run_test tests/builtin-test.c:236\n    #9 0x556701cacfac in test_and_print tests/builtin-test.c:265\n    #10 0x556701cadddb in __cmd_test tests/builtin-test.c:402\n    #11 0x556701caf2aa in cmd_test tests/builtin-test.c:559\n    #12 0x556701d3b557 in run_builtin tools/perf/perf.c:323\n    #13 0x556701d3bac8 in handle_internal_command tools/perf/perf.c:377\n    #14 0x556701d3be90 in run_argv tools/perf/perf.c:421\n    #15 0x556701d3c3f8 in main tools/perf/perf.c:537\n    #16 0x7f2952a46189 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58\n\nSUMMARY: AddressSanitizer: 21 byte(s) leaked in 1 allocation(s).\n```","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"perf tool x86: Fix perf_env memory leak","id":"CVE-2023-53793","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"cifs: fix session state check in reconnect to avoid use-after-free issue","id":"CVE-2023-53794"},"packages":[],"prev":{"headline":"nvme-core: fix memory leak in dhchap_ctrl_secret","id":"CVE-2023-53792"},"products":["Linux"],"published":"2025-12-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A memory leak in the Linux kernel perf tool can lead to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2023-53793/"}