can: isotp: sanitize CAN ID checks in isotp_bind()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 3ea566422cbde9610c2734980d1286ab681bb40e, Kernel 7b4652fc71dcec043977a6def80ef5034c913615, Kernel cf522d741f5301223cc94b978eb1603c7590d65e and 2 more.
In the Linux kernel, the following vulnerability has been resolved: can: isotp: sanitize CAN ID checks in isotp_bind() Syzbot created an environment that lead to a state machine status that can not be reached with a compliant CAN ID address configuration. The provided address information consisted of CAN ID 0x6000001 and 0xC28001 which both boil down to 11 bit CAN IDs 0x001 in sending and receiving. Sanitize the SFF/EFF CAN ID values before performing the address checks.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.10, >=e057dd3fc20ffb3d7f150af46542a51b59b90127 <3ea566422cbde9610c2734980d1286ab681bb40e, >=e057dd3fc20ffb3d7f150af46542a51b59b90127 <7b4652fc71dcec043977a6def80ef5034c913615, >=e057dd3fc20ffb3d7f150af46542a51b59b90127 <cf522d741f5301223cc94b978eb1603c7590d65e, >=e057dd3fc20ffb3d7f150af46542a51b59b90127 <d72866a7f5326160d2a9d945a33eb6ef1883e25d, >=e057dd3fc20ffb3d7f150af46542a51b59b90127 <f343dbe82314ab457153c9afd970be4e9e553020 | 3ea566422cbde9610c2734980d1286ab681bb40e, 7b4652fc71dcec043977a6def80ef5034c913615, cf522d741f5301223cc94b978eb1603c7590d65e, d72866a7f5326160d2a9d945a33eb6ef1883e25d, f343dbe82314ab457153c9afd970be4e9e553020 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket