{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2016-2067 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-2067 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-2067 is a high-severity vulnerability in Google Android, published on 11 Jul 2016. 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-2016-2067 and fix it if it is affected.\n\nWhat it is: CVE-2016-2067 is a high-severity vulnerability in Google Android, published on 11 Jul 2016. 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-2016-2067 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-2016-2067/ (Markdown: https://insights.sbomify.com/CVE-2016-2067/index.md)","id":"CVE-2016-2067","markdown":"https://insights.sbomify.com/CVE-2016-2067/index.md","name":"CVE-2016-2067","record":{"aliases":["GHSA-249p-3p4f-xv9j"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel GPU driver","requires_auth":"none","summary":"Attackers can gain privileges by exploiting mishandled GPU memory flags in the Linux kernel MSM graphics driver.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"android","vendor":"google"},{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"drivers/gpu/msm/kgsl.c in the MSM graphics driver (aka GPU driver) for the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, mishandles the KGSL_MEMFLAGS_GPUREADONLY flag, which allows attackers to gain privileges by leveraging accidental read-write mappings, aka Qualcomm internal bug CR988993.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2020-08-10","github_poc":1,"max_poc_stars":7,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-08-10T23:22:27Z","kind":"github_poc","ref":"https://github.com/hhj4ck/CVE-2016-2067","stars":7,"title":null}],"tier":"poc_unverified"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2016-2067","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"google:android","products":["google:android","linux:linux_kernel"],"type":"privilege_escalation","year":"2016"},"n_packages":0,"n_references":3,"next":{"headline":"Integer overflow in n/a","id":"CVE-2016-2068"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2016-2066"},"products":["n/a"],"published":"2016-07-11","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can gain privileges by exploiting mishandled GPU memory flags in the Linux kernel MSM graphics driver.","url":"https://insights.sbomify.com/CVE-2016-2067/"}