CVE-2026-31570 can: gw: fix OOB heap access in cgw_csum_crc8_rel()

High 8.8 Published Updated

An out-of-bounds heap access in the Linux kernel CAN gateway allows attackers with CAP_NET_ADMIN to potentially execute code or escalate privileges.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-31570?

CVE-2026-31570 is a high-severity memory corruption vulnerability in Linux kernel, published on 24 Apr 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: gw: fix OOB heap access in cgw_csum_crc8_rel()

cgw_csum_crc8_rel() correctly computes bounds-safe indices via calc_idx():

int from = calc_idx(crc8->from_idx, cf->len); int to = calc_idx(crc8->to_idx, cf->len); int res = calc_idx(crc8->result_idx, cf->len);

if (from < 0 || to < 0 || res < 0) return;

However, the loop and the result write then use the raw s8 fields directly instead of the computed variables:

for (i = crc8->from_idx; ...) /* BUG: raw negative index */ cf->data[crc8->result_idx] = ...; /* BUG: raw negative index */

With from_idx = to_idx = result_idx = -64 on a 64-byte CAN FD frame, calc_idx(-64, 64) = 0 so the guard passes, but the loop iterates with i = -64, reading cf->data[-64], and the write goes to cf->data[-64]. This write might end up to 56 (7.0-rc) or 40 (<= 6.19) bytes before the start of the canfd_frame on the heap.

The companion function cgw_csum_xor_rel() uses `from`/`to`/`res` correctly throughout; fix cgw_csum_crc8_rel() to match.

Confirmed with KASAN on linux-7.0-rc2: BUG: KASAN: slab-out-of-bounds in cgw_csum_crc8_rel+0x515/0x5b0 Read of size 1 at addr ffff8880076619c8 by task poc_cgw_oob/62

To configure the can-gw crc8 checksums CAP_NET_ADMIN is needed.

Weakness: CWE-125, CWE-787

Which versions are affected by CVE-2026-31570?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2026-31570?

Apply the vendor's patch.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2026-31570 being exploited?

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

All Linux kernel vulnerabilities

Sources

Also known as AZL-83699, BELL-CVE-2026-31570, DEBIAN-CVE-2026-31570, GHSA-67vp-4p2p-jr3c, ROOT-OS-DEBIAN-11-CVE-2026-31570, ROOT-OS-DEBIAN-12-CVE-2026-31570 and 4 more.

Is CVE-2026-31570 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free