# CVE-2026-72118: can: bcm: fix CAN frame rx/tx statistics

Status: published. Published: 2026-08-15. Updated: 2026-11-06.

In the Linux kernel, the following vulnerability has been resolved:

can: bcm: fix CAN frame rx/tx statistics

KCSAN detected a data race within the bcm_rx_handler() when two CAN frames
have been simultaneously received and processed in a single rx op by two
different CPUs.

Use atomic operations with (signed) long data types to access the
statistics in the hot path to fix the KCSAN complaint.

Additionally simplify the update and check of statistics overflow by
using the atomic operations in separate bcm_update_[rx|tx]_stats()
functions. The rx variant runs under bcm_rx_update_lock to prevent
races when resetting the two rx counters; the tx variant runs under
bcm_tx_lock and only needs to guard its own counter's overflow.

As the rx path resets its values already at LONG_MAX / 100, there is
no conflict between the two locking domains (bcm_rx_update_lock vs.
bcm_tx_lock) even for ops that use both paths.

The rx statistics update and the frames_filtered update in
bcm_rx_changed() were previously performed in two separate
bcm_rx_update_lock sections. For an rx op subscribed on all interfaces
(ifindex == 0), bcm_rx_handler() can run concurrently on different
CPUs, so a counter reset by one CPU between these two sections could
leave frames_filtered larger than frames_abs on another CPU, producing
a bogus (even negative) reduction percentage in procfs. Update the
statistics in the same critical section as bcm_rx_changed() to close
this gap, which also removes the now unneeded extra lock/unlock pair
around the traffic_flags calculation.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ ffd980f976e7fd666c2e61bf8ab35107efd11828; < 640acf3566fc897065127001be875ebc5401c218 (affected, git); ≥ ffd980f976e7fd666c2e61bf8ab35107efd11828; < 47fca0d1620f2d4fab0677564989ef2b9c225c66 (affected, git); ≥ ffd980f976e7fd666c2e61bf8ab35107efd11828; < fd75884eae40a7be47867cbfc9fc84a80bb8ddb4 (affected, git); ≥ ffd980f976e7fd666c2e61bf8ab35107efd11828; < 8b2783172d92edd650de6006ebd1c800937021ab (affected, git); ≥ ffd980f976e7fd666c2e61bf8ab35107efd11828; < 970caff5c1a63702c80e08d920256bcb5f88ecc5 (affected, git); ≥ ffd980f976e7fd666c2e61bf8ab35107efd11828; < 8104bcdb2612fdda95169ddc3b49747b2ff98d24 (affected, git); ≥ ffd980f976e7fd666c2e61bf8ab35107efd11828; < df47f07cdc801a6afe05a486b5a343c3e532a93c (affected, git); ≥ ffd980f976e7fd666c2e61bf8ab35107efd11828; < e6c24ba95fc3f1b5e1dcd28b1c6e59ef61a9daa5 (affected, git). Source: CNA: Linux
- Linux / Linux: 2.6.25 (affected); ≥ 0; < 2.6.25 (unaffected, semver); ≥ 5.10.265; ≤ 5.10.* (unaffected, semver); ≥ 5.15.216; ≤ 5.15.* (unaffected, semver); ≥ 6.1.183; ≤ 6.1.* (unaffected, semver); ≥ 6.6.148; ≤ 6.6.* (unaffected, semver); ≥ 6.12.101; ≤ 6.12.* (unaffected, semver); ≥ 6.18.42; ≤ 6.18.* (unaffected, semver); ≥ 7.1.5; ≤ 7.1.* (unaffected, semver); ≥ 7.2; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: 0.22% as of 2026-11-06; percentile 12.13%

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/640acf3566fc897065127001be875ebc5401c218 (CNA: Linux)

- https://git.kernel.org/stable/c/47fca0d1620f2d4fab0677564989ef2b9c225c66 (CNA: Linux)

- https://git.kernel.org/stable/c/fd75884eae40a7be47867cbfc9fc84a80bb8ddb4 (CNA: Linux)

- https://git.kernel.org/stable/c/8b2783172d92edd650de6006ebd1c800937021ab (CNA: Linux)

- https://git.kernel.org/stable/c/970caff5c1a63702c80e08d920256bcb5f88ecc5 (CNA: Linux)

- https://git.kernel.org/stable/c/8104bcdb2612fdda95169ddc3b49747b2ff98d24 (CNA: Linux)

- https://git.kernel.org/stable/c/df47f07cdc801a6afe05a486b5a343c3e532a93c (CNA: Linux)

- https://git.kernel.org/stable/c/e6c24ba95fc3f1b5e1dcd28b1c6e59ef61a9daa5 (CNA: Linux)

- https://git.kernel.org/stable/c/47fca0d1620f2d4fab0677564989ef2b9c225c66 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/640acf3566fc897065127001be875ebc5401c218 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/8104bcdb2612fdda95169ddc3b49747b2ff98d24 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/8b2783172d92edd650de6006ebd1c800937021ab (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/970caff5c1a63702c80e08d920256bcb5f88ecc5 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/df47f07cdc801a6afe05a486b5a343c3e532a93c (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/e6c24ba95fc3f1b5e1dcd28b1c6e59ef61a9daa5 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/fd75884eae40a7be47867cbfc9fc84a80bb8ddb4 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-72118; retrieved 2026-11-06; source updated 2026-11-06

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72118; retrieved 2026-11-06; source updated 2026-11-06

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-72118; retrieved 2026-11-06; source updated Not reported

Revision: a92aaeba88aad72427fd817a181c056bc4a8a0c5df066e3098bd33acbd53cde2

Canonical: https://y2.dev/cve/CVE-2026-72118

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.