{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-9708 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-9708 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-9708 is a high-severity vulnerability in Google Android, published on 5 Dec 2017. 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-2017-9708 and fix it if it is affected.\n\nWhat it is: CVE-2017-9708 is a high-severity vulnerability in Google Android, published on 5 Dec 2017. 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-2017-9708 in the wild and no public exploit code.\n\nAffected product: Google Android. 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-9708/ (Markdown: https://insights.sbomify.com/CVE-2017-9708/index.md)","id":"CVE-2017-9708","markdown":"https://insights.sbomify.com/CVE-2017-9708/index.md","name":"CVE-2017-9708","record":{"aliases":["GHSA-qqw4-9qp4-r643"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Android camera driver","requires_auth":"low_privilege","summary":"A race condition in the Qualcomm Android camera driver allows concurrent access to shared variables, potentially leading to undefined behavior or system instability.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qualcomm","cpe":[{"product":"android","vendor":"google"}],"cvss":{"score":7,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"In Android for MSM, Firefox OS for MSM, QRD Android, with all Android releases from CAF using the Linux kernel, in the camera driver, the function \"msm_ois_power_down\" is called without a mutex and a race condition can occur in variable \"*reg_ptr\" of sub function \"msm_camera_config_single_vreg\".","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Race condition in Android for MSM, Firefox OS for MSM, QRD Android","id":"CVE-2017-9708","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"google:android","products":["google:android"],"type":"race_condition","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in Android for MSM, Firefox OS for MSM, QRD Android","id":"CVE-2017-9709"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2017-9706"},"products":["Android for MSM, Firefox OS for MSM, QRD Android"],"published":"2017-12-05","related":[{"cvss_score":8.8,"headline":"Google Pixel Improper Authorization","id":"CVE-2026-58704","kev_date_added":"2026-09-16","published":"2026-09-15"},{"cvss_score":8.8,"headline":"Android Runtime Use-After-Free","id":"CVE-2025-48543","kev_date_added":"2025-09-04","published":"2025-09-04"},{"cvss_score":8.8,"headline":"Android Framework Privilege Escalation","id":"CVE-2023-35674","kev_date_added":"2023-09-13","published":"2023-09-11"},{"cvss_score":8.4,"headline":"Android Framework Integer Overflow","id":"CVE-2025-48595","kev_date_added":"2026-06-02","published":"2026-06-01"},{"cvss_score":8.1,"headline":"Android Pixel Privilege Escalation","id":"CVE-2024-32896","kev_date_added":"2024-06-13","published":"2024-06-13"},{"cvss_score":7.8,"headline":"Android Framework Privilege Escalation","id":"CVE-2025-48572","kev_date_added":"2025-12-02","published":"2025-12-08"},{"cvss_score":7.8,"headline":"Android Pixel Privilege Escalation","id":"CVE-2024-29748","kev_date_added":"2024-04-04","published":"2024-04-05"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Qualcomm, Inc."]},"summary":"A race condition in the Qualcomm Android camera driver allows concurrent access to shared variables, potentially leading to undefined behavior or system instability.","url":"https://insights.sbomify.com/CVE-2017-9708/"}