CVE-2026-72114 json
can: bcm: validate frame length in bcm_rx_setup() for RTR replies
published 2026-08-15 2 mo ago modified 2026-10-16 23 d ago also EUVD-2026-59072
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
can: bcm: validate frame length in bcm_rx_setup() for RTR replies
bcm_tx_setup() validates cf->len against the CAN/CAN FD DLC limits before installing frames for TX_SETUP, but bcm_rx_setup() never did the same for the RTR-reply frame configured via RX_SETUP with RX_RTR_FRAME.
Patch / fix
- Linux Linux 5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101, 6.18.42, 7.1.5, 7.2
- linux Debian 12 6.1.187-1
- linux Debian 13 6.12.101-1
- linux Debian 14 7.1.5-1
- linux-6.12 Debian 12 6.12.101-1~deb12u1
debian advisories DEBIAN-CVE-2026-72114
- linux Ubuntu 22.04 LTS 5.15.0-198.208
- linux Ubuntu 24.04 LTS 6.8.0-147.147
- linux Ubuntu 26.04 LTS 7.0.0-38.38
- linux-aws Ubuntu 22.04 LTS 5.15.0-1117.124
- linux-aws Ubuntu 24.04 LTS 6.8.0-1067.70
- linux-aws Ubuntu 26.04 LTS 7.0.0-1014.14
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1118.128
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1071.79
ubuntu advisories UBUNTU-CVE-2026-72114
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/cc1f9569f1c1adf74fa69d6f716a31b58a2fc6ce commit
- git.kernel.org/stable/c/204f2b232717bc470ddb9e1da1d27dd9c6ef0caa commit
- git.kernel.org/stable/c/e061624c0a86c3c26a2bf017e432fbc93ad68f3a commit
- git.kernel.org/stable/c/7d966cdee006911d3957e1a4e72cb93c39cd8c1e commit
- git.kernel.org/stable/c/1b475c0c72f44622a320a4386ce9e76f85e69bc7 commit
- git.kernel.org/stable/c/deb6a697cce3f021e731df543597f37a5e54caab commit
- git.kernel.org/stable/c/59bfddea64159594feb62ef11b7d7a33c8ee3783 commit
- git.kernel.org/stable/c/62ec41f364648be79d54d94d0d240ee326948afd commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-72114 updated cvss 5.5
kernel: can: bcm: validate frame length in bcm_rx_setup() for RTR replies
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: workaround, no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: workaround, no fix available
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 23 d ago
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/cc1f9569f1c1adf74fa69d6f716a31b58a2fc6ce
- git.kernel.org /stable/c/204f2b232717bc470ddb9e1da1d27dd9c6ef0caa
- git.kernel.org /stable/c/e061624c0a86c3c26a2bf017e432fbc93ad68f3a
- git.kernel.org /stable/c/7d966cdee006911d3957e1a4e72cb93c39cd8c1e
- git.kernel.org /stable/c/1b475c0c72f44622a320a4386ce9e76f85e69bc7
- git.kernel.org /stable/c/deb6a697cce3f021e731df543597f37a5e54caab
- git.kernel.org /stable/c/59bfddea64159594feb62ef11b7d7a33c8ee3783
- git.kernel.org /stable/c/62ec41f364648be79d54d94d0d240ee326948afd
Sources
- CVE List CVE-2026-72114
- NVD CVE-2026-72114
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.