{"answers":{"affected":"It affects 11 products.","exploited":"There is no known exploitation of CVE-2025-54601 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-54601 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-54601 is a high-severity vulnerability in Samsung Exynos 1080 Firmware, published on 6 Apr 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-2025-54601 and fix it if it is affected.\n\nWhat it is: CVE-2025-54601 is a high-severity vulnerability in Samsung Exynos 1080 Firmware, published on 6 Apr 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-2025-54601 in the wild and no public exploit code.\n\nAffected product: Samsung Exynos 1080 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-2025-54601/ (Markdown: https://insights.sbomify.com/CVE-2025-54601/index.md)","id":"CVE-2025-54601","markdown":"https://insights.sbomify.com/CVE-2025-54601/index.md","name":"CVE-2025-54601","record":{"aliases":["GHSA-q6xr-vv6x-m5gj"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung Exynos Wi-Fi driver","requires_auth":"low_privilege","summary":"A race condition in the Samsung Exynos Wi-Fi driver allows attackers to trigger a double free via concurrent ioctl calls, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"exynos_1080_firmware","vendor":"samsung"},{"product":"exynos_1280_firmware","vendor":"samsung"},{"product":"exynos_1330_firmware","vendor":"samsung"},{"product":"exynos_1380_firmware","vendor":"samsung"},{"product":"exynos_1480_firmware","vendor":"samsung"},{"product":"exynos_1580_firmware","vendor":"samsung"},{"product":"exynos_850_firmware","vendor":"samsung"},{"product":"exynos_980_firmware","vendor":"samsung"},{"product":"exynos_w1000_firmware","vendor":"samsung"},{"product":"exynos_w920_firmware","vendor":"samsung"},{"product":"exynos_w930_firmware","vendor":"samsung"}],"cvss":{"score":7,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"An issue was discovered in the Wi-Fi driver in Samsung Mobile Processor amd Wearable Processor Exynos 980, 850, 1080, 1280, 1330, 1380, 1480, 1580, W920, W930, and W1000. Improper synchronization on a global variable leads to a double free. An attacker can trigger a race condition by invoking an ioctl function concurrently from multiple threads.","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 n/a","id":"CVE-2025-54601","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"samsung:exynos_1080_firmware","products":["samsung:exynos_1080_firmware","samsung:exynos_1280_firmware","samsung:exynos_1330_firmware","samsung:exynos_1380_firmware","samsung:exynos_1480_firmware","samsung:exynos_850_firmware","samsung:exynos_980_firmware","samsung:exynos_w920_firmware","samsung:exynos_w930_firmware"],"type":"race_condition","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Use after free in n/a","id":"CVE-2025-54602"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2025-54599"},"products":["n/a"],"published":"2026-04-06","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2025-54328","kev_date_added":null,"published":"2026-04-06"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2025-62818","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":9.1,"headline":"Denial of service in n/a","id":"CVE-2025-58349","kev_date_added":null,"published":"2026-04-06"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2025-27807","kev_date_added":null,"published":"2026-01-05"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2025-47202","kev_date_added":null,"published":"2025-07-07"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2025-27891","kev_date_added":null,"published":"2025-05-14"},{"cvss_score":8.8,"headline":"Use after free in n/a","id":"CVE-2025-23102","kev_date_added":null,"published":"2025-06-03"}],"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-04-07","vendors":["n/a"]},"summary":"A race condition in the Samsung Exynos Wi-Fi driver allows attackers to trigger a double free via concurrent ioctl calls, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2025-54601/"}