CVE-2026-72115
Linux CAN bcm race can let injected CAN frames corrupt kernel CAN state and cause DoS
Is CVE-2026-72115 being exploited?
Not confirmed. CVE-2026-72115 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-72115?
CVE-2026-72115 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-72115?
Yes. A fix has been recorded for CVE-2026-72115. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72115 affect?
CVE-2026-72115 affects Linux kernel (can/bcm subsystem), SocketCAN-based systems, CAN-enabled embedded/automotive/industrial devices. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72115?
Update Linux kernel to include bcm fix; isolate CAN interfaces until patched
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote CAN frame injection can race kernel handlers to corrupt bcm rx state, cause spurious RX_TIMEOUTs, clobber frame metadata and produce denial-of-service or kernel instability.
Patch when possible
- affected>= ffd980f976e7fd666c2e61bf8ab35107efd11828 and < f147f48837cb1426521f5b3c3b3134c71128a25d
- affected>= ffd980f976e7fd666c2e61bf8ab35107efd11828 and < 57cf104da4cf450ae9c16801a3164604b801d2cc
- affected>= ffd980f976e7fd666c2e61bf8ab35107efd11828 and < 03dfe347c398fa41a7e30e8dc538f12568c183e6
- affected>= ffd980f976e7fd666c2e61bf8ab35107efd11828 and < 18b45251e74e35668f0dd0c470549384ae191ecf
- affected>= ffd980f976e7fd666c2e61bf8ab35107efd11828 and < 3ff8c24b421070a2db99a5cdb86edc9ff339418e
- affected>= ffd980f976e7fd666c2e61bf8ab35107efd11828 and < eca8b44d51fc6ab61022258ec968e55e3073b79e
- affected>= ffd980f976e7fd666c2e61bf8ab35107efd11828 and < b6317022b685a430a3ae420456716e3c0c02ef4b
- affected>= ffd980f976e7fd666c2e61bf8ab35107efd11828 and < 2f5976f54a04e9f18b25283036ac3136be453b17
- affected2.6.25
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.