{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2026-24083 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-24083 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-24083 is a high-severity memory corruption vulnerability in Qualcomm Qam8295p Firmware, published on 4 Aug 2026. 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-2026-24083 and fix it if it is affected.\n\nWhat it is: CVE-2026-24083 is a high-severity memory corruption vulnerability in Qualcomm Qam8295p Firmware, published on 4 Aug 2026. 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-2026-24083 in the wild and no public exploit code.\n\nAffected product: Qualcomm Qam8295p Firmware. 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-2026-24083/ (Markdown: https://insights.sbomify.com/CVE-2026-24083/index.md)","id":"CVE-2026-24083","markdown":"https://insights.sbomify.com/CVE-2026-24083/index.md","name":"CVE-2026-24083","record":{"aliases":["GHSA-6p34-h594-62rx"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Qualcomm Snapdragon","requires_auth":"low_privilege","summary":"An attacker can exploit memory corruption in Qualcomm Snapdragon device drivers via IOCTL requests to execute arbitrary code or escalate privileges.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qualcomm","cpe":[{"product":"qam8295p_firmware","vendor":"qualcomm"},{"product":"qca6696_firmware","vendor":"qualcomm"},{"product":"sa8295p_firmware","vendor":"qualcomm"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-822","name":"Untrusted Pointer Dereference"}],"description":"Memory Corruption while processing IOCTL device driver requests with invalid arguments.","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":"Untrusted Pointer Dereference in Automotive Security","id":"CVE-2026-24083","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"qualcomm:qam8295p_firmware","products":["qualcomm:qam8295p_firmware","qualcomm:qca6696_firmware","qualcomm:sa8295p_firmware"],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Insecure Security Identifier Mechanism in Multi-Mode Call Processor","id":"CVE-2026-24084"},"packages":[],"prev":{"headline":"Use After Free in Automotive GPU","id":"CVE-2026-24082"},"products":["Snapdragon"],"published":"2026-08-04","related":[{"cvss_score":8.4,"headline":"Use After Free in Automotive Display","id":"CVE-2023-33039","kev_date_added":null,"published":"2023-10-03"},{"cvss_score":8.4,"headline":"Improper Access Control in HAB Memory Management","id":"CVE-2023-21642","kev_date_added":null,"published":"2023-05-02"},{"cvss_score":8.4,"headline":"Improper Validation of Array Index in Automotive Android OS","id":"CVE-2022-40539","kev_date_added":null,"published":"2023-03-07"},{"cvss_score":8.4,"headline":"Improper validation of array index in Android Core","id":"CVE-2022-33274","kev_date_added":null,"published":"2023-01-06"},{"cvss_score":8.4,"headline":"Improper input validation in Automotive Android OS","id":"CVE-2022-33300","kev_date_added":null,"published":"2023-01-06"},{"cvss_score":8.4,"headline":"Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile","id":"CVE-2021-35126","kev_date_added":null,"published":"2022-06-14"}],"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":"total"},"state":"PUBLISHED","updated":"2026-08-05","vendors":["Qualcomm, Inc."]},"summary":"An attacker can exploit memory corruption in Qualcomm Snapdragon device drivers via IOCTL requests to execute arbitrary code or escalate privileges.","url":"https://insights.sbomify.com/CVE-2026-24083/"}