# CVE-2026-0461: Memory corruption in Kria SOMs

> Attackers can execute unauthorized code during boot via buffer overflow in USB DFU handling on AMD Zynq devices.

- **Severity:** High 7.5 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-2xg6-gqcc-77jw

## What is CVE-2026-0461?

CVE-2026-0461 is a high-severity memory corruption vulnerability in AMD Kria SOMs, published on 5 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insufficient boundary validation in the USB boot mode implementation of AMD Zynq™ UltraScale+ MPSoC and RFSoC devices could allow unbounded Device Firmware Upgrade (DFU) download requests to overflow the DDR receive buffer into FSBL memory, potentially resulting in unauthorized code execution during the boot process. This issue could impact the confidentiality, integrity, or availability of affected system.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

No fix has been published for CVE-2026-0461 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-0461 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-0461 is a high-severity memory corruption vulnerability in AMD Kria SOMs, published on 5 Oct 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-0461 in the wild and no public exploit code.

Affected product: AMD Kria SOMs. 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-0461/ (Markdown: https://insights.sbomify.com/CVE-2026-0461/index.md)
```

## Sources

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

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