# CVE-2026-80706: can: softing: fw_parse(): validate firmware record spans

> A missing bounds check in the Linux kernel CAN softing driver allows out-of-bounds reads and writes via crafted firmware, potentially leading to code execution or crashes.

- **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:** 28 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** AZL-98099, BELL-CVE-2026-80706, DEBIAN-CVE-2026-80706, GHSA-q4rv-gqhg-3pm9, UBUNTU-CVE-2026-80706

## What is CVE-2026-80706?

CVE-2026-80706 is a high-severity memory corruption vulnerability in Linux, published on 28 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:

can: softing: fw_parse(): validate firmware record spans

fw_parse() reads a fixed record header, a firmware-provided payload,
and a trailing checksum without knowing the end of the firmware blob. A
truncated record can therefore make those reads exceed the blob.

The same record also supplies addresses and lengths for writes into
DPRAM. The generic loader uses wrap-prone mixed signed arithmetic for its
bounds check, while the application loader does not bound the staging
copy at all.

Pass the firmware end to the parser and validate the full source record.
Use a signed wide offset for generic DPRAM records and validate the
application staging span against the mapped DPRAM before copying.

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


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

Apply the vendor's patch.

## Is CVE-2026-80706 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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