Node hang via unacknowledged mismatched-RTR CAN frame
Published Oct 31, 2022 · Updated May 5, 2025
Denial of service in the Bosch M_CAN driver in Zephyr RTOS 3.1 and earlier allows remote attackers to hang nodes via a crafted CAN frame. The interrupt service routine fails to acknowledge a received frame when its RTR bit differs from a matching software filter, so the hardware FIFO returns the same frame indefinitely. The attacker needs access to the same CAN network and a node using the Bosch M_CAN back end; the endless interrupt loop prevents normal node operation.
Summary
What happened
Denial of service in the Bosch M_CAN driver in Zephyr RTOS 3.1 and earlier allows remote attackers to hang nodes via a crafted CAN frame. The interrupt service routine fails to acknowledge a received frame when its RTR bit differs from a matching software filter, so the hardware FIFO returns the same frame indefinitely. The attacker needs access to the same CAN network and a node using the Bosch M_CAN back end; the endless interrupt loop prevents normal node operation.
The record
- CVE
- CVE-2022-2741
- Published
- Oct 31, 2022
- Updated
- May 5, 2025
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-400, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 31, 2022CVE publishedPublication date reported by the CVE source.
- May 5, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=v3.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo