# CVE-2026-72158: fpga: dfl: add bounds check in dfh_get_param_size()

> A missing bounds check in the Linux kernel FPGA driver allows a malicious device to trigger memory corruption via crafted headers, potentially leading to system crashes or code execution.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-72158, DEBIAN-CVE-2026-72158, GHSA-765f-xmg8-8m66, UBUNTU-CVE-2026-72158

## What is CVE-2026-72158?

CVE-2026-72158 is a memory corruption vulnerability in Linux, published on 15 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:

fpga: dfl: add bounds check in dfh_get_param_size()

dfh_get_param_size() can return a parameter size larger than the feature
region because the loop bounds check is evaluated before incrementing
size. If the EOP (End of Parameters) bit is set in the same iteration,
the inflated size is returned without re-validation against max.

This can cause create_feature_instance() to call memcpy_fromio() with a
size exceeding the ioremap'd region when a malicious FPGA device provides
crafted DFHv1 parameter headers.

Add a bounds check after the size increment to ensure the accumulated
size never exceeds the feature boundary.

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


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

Apply the vendor's patch.

## Is CVE-2026-72158 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72158 is a memory corruption vulnerability in Linux, published on 15 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-72158 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-72158/ (Markdown: https://insights.sbomify.com/CVE-2026-72158/index.md)
```

## Sources

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

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