{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-6259 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2017-6259 is a medium-severity denial of service vulnerability in Nvidia Gpu Driver, published on 28 Jul 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-6259 and fix it if it is affected.\n\nWhat it is: CVE-2017-6259 is a medium-severity denial of service vulnerability in Nvidia Gpu Driver, published on 28 Jul 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-6259 in the wild and no public exploit code.\n\nAffected product: Nvidia Gpu Driver. 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-2017-6259/ (Markdown: https://insights.sbomify.com/CVE-2017-6259/index.md)","id":"CVE-2017-6259","markdown":"https://insights.sbomify.com/CVE-2017-6259/index.md","name":"CVE-2017-6259","record":{"aliases":["DEBIAN-CVE-2017-6259","GHSA-h9mp-66gm-w56r","UBUNTU-CVE-2017-6259"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"NVIDIA GPU Driver","requires_auth":"none","summary":"An attacker can cause a denial of service in NVIDIA GPU drivers by triggering an invalid state in the kernel mode layer handler.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"nvidia","cpe":[{"product":"gpu_driver","vendor":"nvidia"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:N/A:H","version":"3.0"},"cwes":[],"description":"NVIDIA GPU Display Driver contains a vulnerability in the kernel mode layer handler where an incorrect detection and recovery from an invalid state produced by specific user actions may lead to denial of service.","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":"Denial of service in NVIDIA GPU Display Driver","id":"CVE-2017-6259","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"nvidia:gpu_driver","products":["nvidia:gpu_driver"],"type":"denial_of_service","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in NVIDIA Windows GPU Display Driver","id":"CVE-2017-6260"},"packages":[],"prev":{"headline":"Memory corruption in Android","id":"CVE-2017-6258"},"products":["NVIDIA GPU Display Driver"],"published":"2017-07-28","related":[{"cvss_score":10,"headline":"Memory corruption in GPU Display Driver","id":"CVE-2019-5684","kev_date_added":null,"published":"2019-08-06"},{"cvss_score":10,"headline":"Privilege escalation in n/a","id":"CVE-2015-5053","kev_date_added":null,"published":"2015-11-24"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2013-5986","kev_date_added":null,"published":"2014-01-21"},{"cvss_score":9.8,"headline":"Memory corruption in GPU Display Driver","id":"CVE-2019-5685","kev_date_added":null,"published":"2019-08-06"},{"cvss_score":8.8,"headline":"Null dereference in GPU Display Driver","id":"CVE-2018-6247","kev_date_added":null,"published":"2018-04-02"},{"cvss_score":8.8,"headline":"Memory corruption in GPU Display Driver","id":"CVE-2018-6248","kev_date_added":null,"published":"2018-04-02"},{"cvss_score":8.8,"headline":"Null dereference in GPU Display Driver","id":"CVE-2018-6249","kev_date_added":null,"published":"2018-04-02"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Nvidia Corporation"]},"summary":"An attacker can cause a denial of service in NVIDIA GPU drivers by triggering an invalid state in the kernel mode layer handler.","url":"https://insights.sbomify.com/CVE-2017-6259/"}