{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2025-23275 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-23275 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-23275 is a medium-severity memory corruption vulnerability in NVIDIA CUDA Toolkit, published on 24 Sep 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-23275 and fix it if it is affected.\n\nWhat it is: CVE-2025-23275 is a medium-severity memory corruption vulnerability in NVIDIA CUDA Toolkit, published on 24 Sep 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-23275 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-23275/ (Markdown: https://insights.sbomify.com/CVE-2025-23275/index.md)","id":"CVE-2025-23275","markdown":"https://insights.sbomify.com/CVE-2025-23275/index.md","name":"CVE-2025-23275","record":{"aliases":["DEBIAN-CVE-2025-23275","GHSA-rrw2-mp24-c2pg","UBUNTU-CVE-2025-23275"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"CUDA Toolkit nvJPEG","requires_auth":"low_privilege","summary":"A local authenticated user can trigger a GPU out-of-bounds write in nvJPEG, causing denial of service and information disclosure.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"nvidia","cpe":[{"product":"cuda_toolkit","vendor":"nvidia"},{"product":"nvjpeg","vendor":"nvidia"}],"cvss":{"score":4.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"NVIDIA CUDA Toolkit for all platforms contains a vulnerability in nvJPEG where a local authenticated user may cause a GPU out-of-bounds write by providing certain image dimensions.  A successful exploit of this vulnerability may lead to denial of service and information disclosure.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Memory corruption in NVIDIA CUDA Toolkit","id":"CVE-2025-23275","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Privilege escalation in GPU Display Drivers","id":"CVE-2025-23276"},"packages":[],"prev":{"headline":"Integer overflow in NVIDIA CUDA Toolkit","id":"CVE-2025-23274"},"products":["NVIDIA CUDA Toolkit","nvJPEG"],"published":"2025-09-24","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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-24","vendors":["NVIDIA"]},"summary":"A local authenticated user can trigger a GPU out-of-bounds write in nvJPEG, causing denial of service and information disclosure.","url":"https://insights.sbomify.com/CVE-2025-23275/"}