{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2022-22265 in the wild since at least 18 Sep 2023.","fix":"No fix has been published for CVE-2022-22265 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 9 Oct 2023.","what":"CVE-2022-22265 is a medium-severity memory corruption vulnerability in Google Android, published on 7 Jan 2022. 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-2022-22265 and fix it if it is affected.\n\nWhat it is: CVE-2022-22265 is a medium-severity memory corruption vulnerability in Google Android, published on 7 Jan 2022. 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: Yes. Attackers have exploited CVE-2022-22265 in the wild since at least 18 Sep 2023.\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-2022-22265/ (Markdown: https://insights.sbomify.com/CVE-2022-22265/index.md)","id":"CVE-2022-22265","markdown":"https://insights.sbomify.com/CVE-2022-22265/index.md","name":"CVE-2022-22265","record":{"aliases":["GHSA-9fvj-4grr-mv9j"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung mobile device","requires_auth":"low_privilege","summary":"A vulnerability in the NPU driver allows arbitrary memory write and code execution on Samsung mobile devices.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Samsung Mobile","cpe":[{"product":"android","vendor":"google"}],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-703","name":"Improper Check or Handling of Exceptional Conditions"}],"description":"An improper check or handling of exceptional conditions in NPU driver prior to SMR Jan-2022 Release 1 allows arbitrary memory write and code execution.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"exploited"},"has_fix":null,"headline":"Samsung Mobile Devices Use-After-Free","id":"CVE-2022-22265","indexable":true,"kev":{"dateAdded":"2023-09-18","dueDate":"2023-10-09","knownRansomwareCampaignUse":"Unknown","product":"Mobile Devices","requiredAction":"Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.","vendorProject":"Samsung","vulnerabilityName":"Samsung Mobile Devices Use-After-Free Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"google:android","products":["google:android"],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in Samsung Mobile Devices","id":"CVE-2022-22266"},"packages":[],"prev":{"headline":"Path traversal in Samsung Mobile Devices","id":"CVE-2022-22264"},"products":["Samsung Mobile Devices"],"published":"2022-01-07","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":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"active","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-21","vendors":["Samsung Mobile"]},"summary":"A vulnerability in the NPU driver allows arbitrary memory write and code execution on Samsung mobile devices.","url":"https://insights.sbomify.com/CVE-2022-22265/"}