# CVE-2026-68401: firmware: arm_ffa: Fix out-of-bound writes in ffa_setup_and_transmit()

> Out-of-bound writes in the ARM FFA firmware driver allow attackers to corrupt memory, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-94838, BELL-CVE-2026-68401, DEBIAN-CVE-2026-68401, GHSA-hvgp-9g43-gqqw, UBUNTU-CVE-2026-68401

## What is CVE-2026-68401?

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.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

firmware: arm_ffa: Fix out-of-bound writes in ffa_setup_and_transmit()

Sashiko (locally) reports multiple out-of-bound issues in
ffa_setup_and_transmit:
1) Writing ep_mem_access->reserved can write out of bounds for FFA
   versions < 1.2 as ffa_emad_size_get() returns 16 bytes in that case
   while reserved has an offset of 24.
   Instead of zeroing fields, memset the struct to zero first based on
   the FFA version.

2) Make sure there is enough size to write constituents.

While at it, convert the only sizeof() in the driver that uses a
type instead of variable.

## Which versions are affected by CVE-2026-68401?


## How do I fix CVE-2026-68401?

Apply the vendor's patch.

## Is CVE-2026-68401 being exploited?

There is no known exploitation of CVE-2026-68401 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68401 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2026-68401 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68401/ (Markdown: https://insights.sbomify.com/CVE-2026-68401/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68401
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68401
- OSV: https://osv.dev/vulnerability/CVE-2026-68401

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68401/
Summaries are generated and may contain mistakes; the official description above is the record.