Service interruption via unsanitized CAN ID comparison
Published Feb 26, 2025 · Updated May 11, 2026
Improper CAN ID validation in the Linux kernel ISO-TP module allows local users to interrupt service through a crafted socket binding. The isotp_bind() path compares raw receive and transmit CAN identifiers before masking SFF/EFF flag bits, so distinct noncompliant inputs can collapse to the same 11-bit ID after validation and place the state machine in an unreachable status. Low-privileged local access and creation of a CAN ISO-TP socket are required; the published analysis identifies availability loss but not a specific hang, crash, reboot, or shutdown.
Summary
What happened
Improper CAN ID validation in the Linux kernel ISO-TP module allows local users to interrupt service through a crafted socket binding. The isotp_bind() path compares raw receive and transmit CAN identifiers before masking SFF/EFF flag bits, so distinct noncompliant inputs can collapse to the same 11-bit ID after validation and place the state machine in an unreachable status. Low-privileged local access and creation of a CAN ISO-TP socket are required; the published analysis identifies availability loss but not a specific hang, crash, reboot, or shutdown.
The record
- CVE
- CVE-2022-49269
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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=5.10
- Affected versionversion=e057dd3fc20ffb3d7f150af46542a51b59b90127 <3ea566422cbde9610c2734980d1286ab681bb40e
- Affected versionversion=e057dd3fc20ffb3d7f150af46542a51b59b90127 <7b4652fc71dcec043977a6def80ef5034c913615
- Affected versionversion=e057dd3fc20ffb3d7f150af46542a51b59b90127 <cf522d741f5301223cc94b978eb1603c7590d65e
- Affected versionversion=e057dd3fc20ffb3d7f150af46542a51b59b90127 <d72866a7f5326160d2a9d945a33eb6ef1883e25d
- Affected versionversion=e057dd3fc20ffb3d7f150af46542a51b59b90127 <f343dbe82314ab457153c9afd970be4e9e553020
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
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