{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-23247 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-23247 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-23247 is a medium-severity memory corruption vulnerability in NVIDIA CUDA Toolkit, published on 27 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-23247 and fix it if it is affected.\n\nWhat it is: CVE-2025-23247 is a medium-severity memory corruption vulnerability in NVIDIA CUDA Toolkit, published on 27 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-23247 in the wild and no public exploit code.\n\nAffected product: NVIDIA CUDA Toolkit. 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-2025-23247/ (Markdown: https://insights.sbomify.com/CVE-2025-23247/index.md)","id":"CVE-2025-23247","markdown":"https://insights.sbomify.com/CVE-2025-23247/index.md","name":"CVE-2025-23247","record":{"aliases":["DEBIAN-CVE-2025-23247","GHSA-mhvp-2g8x-v832","UBUNTU-CVE-2025-23247"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"CUDA Toolkit","requires_auth":"none","summary":"A buffer length check failure in the cuobjdump binary allows attackers to execute arbitrary code or cause a crash via a malformed ELF file.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"nvidia","cpe":[{"product":"cuda_toolkit","vendor":"nvidia"}],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-130","name":"Improper Handling of Length Parameter Inconsistency"}],"description":"NVIDIA CUDA Toolkit for all platforms contains a vulnerability in the cuobjdump binary, where a failure to check the length of a buffer could allow a user to cause the tool to crash or execute arbitrary code by passing in a malformed ELF file. A successful exploit of this vulnerability might lead to arbitrary code execution.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-11-20","github_poc":1,"max_poc_stars":3,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-11-20T15:53:07Z","kind":"github_poc","ref":"https://github.com/SpiralBL0CK/CVE-2025-23247","stars":3,"title":"wip for CVE-2025-23247 . ATM just crash PoC which shows we control buffer and offset, so we got aaw "}],"tier":"poc_unverified"},"has_fix":false,"headline":"Memory corruption in NVIDIA CUDA Toolkit","id":"CVE-2025-23247","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in NVIDIA CUDA Toolkit","id":"CVE-2025-23248"},"packages":[],"prev":{"headline":"Denial of service in vGPU Software, Cloud Gaming","id":"CVE-2025-23246"},"products":["NVIDIA CUDA Toolkit"],"published":"2025-05-27","related":[{"cvss_score":7.8,"headline":"Integer overflow in NVIDIA CUDA Toolkit","id":"CVE-2022-21821","kev_date_added":null,"published":"2022-03-29"},{"cvss_score":7.8,"headline":"Memory corruption in NVIDIA CUDA Toolkit","id":"CVE-2020-5991","kev_date_added":null,"published":"2020-10-30"},{"cvss_score":7.3,"headline":"Command injection in CUDA Toolkit","id":"CVE-2025-33228","kev_date_added":null,"published":"2026-01-20"},{"cvss_score":7.3,"headline":"Code injection in CUDA Toolkit","id":"CVE-2025-33229","kev_date_added":null,"published":"2026-01-20"},{"cvss_score":7.3,"headline":"Command injection in CUDA Toolkit","id":"CVE-2025-33230","kev_date_added":null,"published":"2026-01-20"},{"cvss_score":6.7,"headline":"Other in CUDA Toolkit","id":"CVE-2025-33231","kev_date_added":null,"published":"2026-01-20"},{"cvss_score":5.3,"headline":"Memory corruption in NVIDIA CUDA Toolkit","id":"CVE-2023-25512","kev_date_added":null,"published":"2023-04-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-06-02","vendors":["NVIDIA"]},"summary":"A buffer length check failure in the cuobjdump binary allows attackers to execute arbitrary code or cause a crash via a malformed ELF file.","url":"https://insights.sbomify.com/CVE-2025-23247/"}