CVE Intelligence
High Memory corruption

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

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.

Published Apr 24, 2026 · Updated Oct 16, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.4% (30-day exploitation probability)+5
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.41%
ahead of 34% of scored CVEs · Oct 16, 2026
Affects
Linux
Linux and 1 more
CVSS base
8.8
High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Linux Linux version 5.4≥ 456a8a646b2563438c16a9b27decf9aa717f1ebb and < b9c310d72783cc2f30d103eed83920a5a29c671a≥ 456a8a646b2563438c16a9b27decf9aa717f1ebb and < 66b689efd08227da2c5ca49b58b30a95d23c695a≥ 456a8a646b2563438c16a9b27decf9aa717f1ebb and < 84f8b76d24273175a22713e83e90874e1880d801≥ 456a8a646b2563438c16a9b27decf9aa717f1ebb and < c4e8eaa75fa0b6bcbfa5356d6195c4ad0e05e57a≥ 456a8a646b2563438c16a9b27decf9aa717f1ebb and < 54ecdf76a55e75c1f5085e440f8ab671a3283ef5≥ 456a8a646b2563438c16a9b27decf9aa717f1ebb and < a025283d7f7404c739225e457fb99db2368bb544≥ 456a8a646b2563438c16a9b27decf9aa717f1ebb and < 999ca48d55a8a46da21519db7e834e5867200379
and 1 more ≥ 456a8a646b2563438c16a9b27decf9aa717f1ebb and < e7c99348b0612b2bc02d5ce6ff9873261cc7605f
Vulnerable CVE Program (cve.org) e CISA ADP
Linux Linux Kernel version 7.0-rc5version 7.0-rc7version 7.0-rc6≥ 5.4.1 and < 5.10.253version 7.0-rc4version 7.0-rc3version 7.0-rc2version 7.0-rc1
and 7 more version 5.4≥ 6.19 and < 6.19.11≥ 6.13 and < 6.18.21≥ 6.7 and < 6.12.80≥ 6.2 and < 6.6.131≥ 5.16 and < 6.1.168≥ 5.11 and < 5.15.203
Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Adjacent
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.8 CVSS 3.1 High 2.8 5.9 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database
8.8 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
8.8 CVSS 3.1 High — — Linux via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-125 · Out-of-bounds Read

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 16, 2026 · 4 reading(s) · max 0.41%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
endpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 16, 2026 · CVE Program (cve.org) e CISA ADP
  • Affected products added · linux/linux
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 8.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Apr 24, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 16, 2026 – Oct 16, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

10 on the record

Elsewhere on this site

Linux
every CVE for this vendor
Memory corruption
same class
CWE-125
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-99999 ipv4: validate checksum_start before completing checksum 1d
  • CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 1d
  • CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 2d
  • CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 2d
  • CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 2d
  • CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-31570 is "can: gw: fix OOB heap access in cgw_csum_crc8_rel()", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. EPSS 0.41% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.