can: replace ARPHRD_CAN type checks with can_get_ml_priv()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 5.5, Kernel 27edc672a80ae9d5e7e8aa0cc8f5e3ed2b5dab19, Kernel 962947b69589881167054bae5accc8abfd5aa4b6 and 7 more.
In the Linux kernel, the following vulnerability has been resolved: can: replace ARPHRD_CAN type checks with can_get_ml_priv() Commit 4e096a18867a ("net: introduce CAN specific pointer in the struct net_device") introduced an explicit way to assign the midlayer private pointer (dev->ml_priv) to named users like ML_PRIV_CAN. A valid pointer returned by can_get_ml_priv() therefore identifies a real CAN device. The referenced commit only converted the j1939 and proc code to this check, while the other parts of the CAN subsystem still rely on dev->type == ARPHRD_CAN. The TUNSETLINK ioctl allows a down TUN/TAP device to set its hardware type to ARPHRD_CAN while dev->ml_priv remains NULL. Such a repurposed netdevice passes the ARPHRD_CAN checks. Commit 8aa59e355949 ("can: af_can: fix NULL pointer dereference in can_rx_register()") already made can_rx_register() reject such devices. But can_rx_unregister() still only checks dev->type and dereferences the NULL ml_priv when it walks the receive lists of the device. CAN_ISOTP reaches this path: isotp_bind() ignores the return values of can_rx_register() and binds the socket anyway. When the socket is released or the device is unregistered, isotp_release() and isotp_notify() remove the filters that have never been registered and trigger the NULL pointer dereference in can_rx_unregister(). This only requires owning a TUN/TAP device or CAP_NET_ADMIN in an unprivileged user namespace. Convert the remaining ARPHRD_CAN checks in af_can, bcm, gw, isotp and raw to can_get_ml_priv().
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=5.4.110 <5.5, >=4e096a18867a5a989b510f6999d9c6b6622e8f7b <27edc672a80ae9d5e7e8aa0cc8f5e3ed2b5dab19, >=4e096a18867a5a989b510f6999d9c6b6622e8f7b <962947b69589881167054bae5accc8abfd5aa4b6, >=4e096a18867a5a989b510f6999d9c6b6622e8f7b <c693cbfbc2ad5ab159c671c58f285aa3d4d8a98b, >=4e096a18867a5a989b510f6999d9c6b6622e8f7b <f4910431fdf7b2800f0bec9f161900511f9a8bcd, >=5.10.28 <5.11, >=5.11.12 <5.12, =1a5751d58b14195f763b8c1d9ef33fb8a93e95e7, =4ac1feff6ea6495cbfd336f4438a6c6d140544a6, =5.12, =96340078d50a54f6a1252c62596bc44321c8bff9 | 5.5, 27edc672a80ae9d5e7e8aa0cc8f5e3ed2b5dab19, 962947b69589881167054bae5accc8abfd5aa4b6, c693cbfbc2ad5ab159c671c58f285aa3d4d8a98b, f4910431fdf7b2800f0bec9f161900511f9a8bcd, 5.11, 5.12 |
| linux-kernel: Kernel | >=5.11.12 <5.12, >=5.12.0 <6.12.118, >=5.4.110 <5.5, >=6.13.0 <6.18.64, >=6.19.0 <7.3.5, >=5.10.28 <5.11 | 5.12, 6.12.118, 5.5, 6.18.64, 7.3.5, 5.11 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket