{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54123 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54123 is a memory corruption vulnerability in Linux, published on 24 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-54123 and fix it if it is affected.\n\nWhat it is: CVE-2023-54123 is a memory corruption vulnerability in Linux, published on 24 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-54123 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-54123/ (Markdown: https://insights.sbomify.com/CVE-2023-54123/index.md)","id":"CVE-2023-54123","markdown":"https://insights.sbomify.com/CVE-2023-54123/index.md","name":"CVE-2023-54123","record":{"aliases":["BELL-CVE-2023-54123","DEBIAN-CVE-2023-54123","GHSA-fggm-fgvr-h4xg","UBUNTU-CVE-2023-54123"],"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":"none","summary":"A memory leak in the Linux kernel RAID10 driver allows local attackers to exhaust system memory, potentially causing a 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\nmd/raid10: fix memleak for 'conf-\u003ebio_split'\n\nIn the error path of raid10_run(), 'conf' need be freed, however,\n'conf-\u003ebio_split' is missed and memory will be leaked.\n\nSince there are 3 places to free 'conf', factor out a helper to fix the\nproblem.","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":"md/raid10: fix memleak for 'conf-\u003ebio_split'","id":"CVE-2023-54123","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":8,"next":{"headline":"f2fs: fix to drop all dirty pages during umount() if cp_error is set","id":"CVE-2023-54124"},"packages":[],"prev":{"headline":"drm/msm/dpu: Add check for cstate","id":"CVE-2023-54122"},"products":["Linux"],"published":"2025-12-24","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 RAID10 driver allows local attackers to exhaust system memory, potentially causing a denial of service.","url":"https://insights.sbomify.com/CVE-2023-54123/"}