{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54171 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54171 is a memory corruption vulnerability in Linux, published on 30 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-54171 and fix it if it is affected.\n\nWhat it is: CVE-2023-54171 is a memory corruption vulnerability in Linux, published on 30 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-54171 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-54171/ (Markdown: https://insights.sbomify.com/CVE-2023-54171/index.md)","id":"CVE-2023-54171","markdown":"https://insights.sbomify.com/CVE-2023-54171/index.md","name":"CVE-2023-54171","record":{"aliases":["BELL-CVE-2023-54171","DEBIAN-CVE-2023-54171","GHSA-rgpm-wqmc-fmj4","UBUNTU-CVE-2023-54171"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A memory leak in the Linux kernel tracing subsystem allows local attackers to exhaust system memory by repeatedly reading trace_pipe, causing 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\ntracing: Fix memory leak of iter-\u003etemp when reading trace_pipe\n\nkmemleak reports:\n  unreferenced object 0xffff88814d14e200 (size 256):\n    comm \"cat\", pid 336, jiffies 4294871818 (age 779.490s)\n    hex dump (first 32 bytes):\n      04 00 01 03 00 00 00 00 08 00 00 00 00 00 00 00  ................\n      0c d8 c8 9b ff ff ff ff 04 5a ca 9b ff ff ff ff  .........Z......\n    backtrace:\n      [\u003cffffffff9bdff18f\u003e] __kmalloc+0x4f/0x140\n      [\u003cffffffff9bc9238b\u003e] trace_find_next_entry+0xbb/0x1d0\n      [\u003cffffffff9bc9caef\u003e] trace_print_lat_context+0xaf/0x4e0\n      [\u003cffffffff9bc94490\u003e] print_trace_line+0x3e0/0x950\n      [\u003cffffffff9bc95499\u003e] tracing_read_pipe+0x2d9/0x5a0\n      [\u003cffffffff9bf03a43\u003e] vfs_read+0x143/0x520\n      [\u003cffffffff9bf04c2d\u003e] ksys_read+0xbd/0x160\n      [\u003cffffffff9d0f0edf\u003e] do_syscall_64+0x3f/0x90\n      [\u003cffffffff9d2000aa\u003e] entry_SYSCALL_64_after_hwframe+0x6e/0xd8\n\nwhen reading file 'trace_pipe', 'iter-\u003etemp' is allocated or relocated\nin trace_find_next_entry() but not freed before 'trace_pipe' is closed.\n\nTo fix it, free 'iter-\u003etemp' in tracing_release_pipe().","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":"tracing: Fix memory leak of iter-\u003etemp when reading trace_pipe","id":"CVE-2023-54171","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":5,"next":{"headline":"x86/hyperv: Disable IBT when hypercall page lacks ENDBR instruction","id":"CVE-2023-54172"},"packages":[],"prev":{"headline":"keys: Fix linking a duplicate key to a keyring's assoc_array","id":"CVE-2023-54170"},"products":["Linux"],"published":"2025-12-30","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 tracing subsystem allows local attackers to exhaust system memory by repeatedly reading trace_pipe, causing denial of service.","url":"https://insights.sbomify.com/CVE-2023-54171/"}