# CVE-2026-80617: net: airoha: fix foe_check_time allocation size

> A heap buffer overflow in the Airoha PPE driver allows attackers to cause a kernel crash via improper memory allocation.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 29 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-80617, GHSA-9xc5-vpm2-h2hw, UBUNTU-CVE-2026-80617

## What is CVE-2026-80617?

CVE-2026-80617 is a critical memory corruption vulnerability in Linux, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

net: airoha: fix foe_check_time allocation size

foe_check_time is declared as u16 pointer but was allocated with
only ppe_num_entries bytes instead of ppe_num_entries * sizeof(u16).

When airoha_ppe_foe_verify_entry() is called with hash >= ppe_num_entries/2,
it writes beyond the allocated buffer, causing heap buffer overflow and
potential kernel crash.

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


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

Apply the vendor's patch.

## Is CVE-2026-80617 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80617 is a critical memory corruption vulnerability in Linux, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80617 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-80617/ (Markdown: https://insights.sbomify.com/CVE-2026-80617/index.md)
```

## Sources

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

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