In the Linux kernel, the following vulnerability has been resolved:
can: bcm: extend bcm_tx_lock usage for data and timer updates
Stage new CAN frame content for an existing tx op into a kmalloc()d buffer and validate it there, mirroring the approach already used in bcm_rx_setup(). Only copy the validated data into op->frames while holding op->bcm_tx_lock, so bcm_can_tx() and bcm_tx_timeout_handler() can no longer observe a partially updated or unvalidated frame.
Add a missing error path for memcpy_from_msg() when copying CAN frame data from userspace.
Also move the kt_ival1/kt_ival2/ival1/ival2 updates in bcm_tx_setup() under op->bcm_tx_lock, and read kt_ival1/kt_ival2/count under the same lock in bcm_tx_set_expiry() and bcm_tx_timeout_handler(), closing the torn 64-bit ktime_t read on 32-bit platforms.
References
- https://git.kernel.org/stable/c/12ce799f7ab1e05bd8fbf79e46f403bfe5597ebc
- https://git.kernel.org/stable/c/337f966c00662d81ad82cf5a4bbb150b2e32c0d4
- https://git.kernel.org/stable/c/52f06e7603780de100233713ddaf971d422e10ef
- https://git.kernel.org/stable/c/972fd66bb08fdef1090abe43196ca8da07216d13
- https://git.kernel.org/stable/c/bd46f55dec608daa44b45dcf3328517630ad8e40