{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68401 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68401 is a high-severity memory corruption vulnerability in Linux, published on 10 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-68401 and fix it if it is affected.\n\nWhat it is: CVE-2026-68401 is a high-severity memory corruption vulnerability in Linux, published on 10 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-68401 in the wild and no public exploit code.\n\nAffected product: Linux. 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-68401/ (Markdown: https://insights.sbomify.com/CVE-2026-68401/index.md)","id":"CVE-2026-68401","markdown":"https://insights.sbomify.com/CVE-2026-68401/index.md","name":"CVE-2026-68401","record":{"aliases":["AZL-94838","BELL-CVE-2026-68401","DEBIAN-CVE-2026-68401","GHSA-hvgp-9g43-gqqw","UBUNTU-CVE-2026-68401"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"Out-of-bound writes in the ARM FFA firmware driver allow attackers to corrupt memory, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"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":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_ffa: Fix out-of-bound writes in ffa_setup_and_transmit()\n\nSashiko (locally) reports multiple out-of-bound issues in\nffa_setup_and_transmit:\n1) Writing ep_mem_access-\u003ereserved can write out of bounds for FFA\n   versions \u003c 1.2 as ffa_emad_size_get() returns 16 bytes in that case\n   while reserved has an offset of 24.\n   Instead of zeroing fields, memset the struct to zero first based on\n   the FFA version.\n\n2) Make sure there is enough size to write constituents.\n\nWhile at it, convert the only sizeof() in the driver that uses a\ntype instead of variable.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"firmware: arm_ffa: Fix out-of-bound writes in ffa_setup_and_transmit()","id":"CVE-2026-68401","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"wifi: cfg80211: bound element ID read when checking non-inheritance","id":"CVE-2026-68402"},"packages":[],"prev":{"headline":"firmware: arm_ffa: Fix Endpoint Memory Access Descriptor offset calculation","id":"CVE-2026-68400"},"products":["Linux"],"published":"2026-08-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"Out-of-bound writes in the ARM FFA firmware driver allow attackers to corrupt memory, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-68401/"}