CVE-2026-72119
HighCVSS 7.8Exploitation Probability (EPSS)
Low risk6th percentile - higher than 6% of all known CVEs
Summary
In the Linux kernel, the CAN BCM module extends the use of bcm_tx_lock for data and timer updates. New frame data is first validated in a separate buffer and then copied under the lock, preventing observation of partially updated frames. Error handling for memcpy_from_msg() was added, and timer updates were moved under the lock, eliminating torn 64-bit reads on 32-bit platforms.
Risk Assessment
The patch eliminates potential races and data tearing, improving stability and security of CAN systems.
Recommendation
Apply the kernel patch that introduces the above changes in the CAN BCM module.
Original NVD description (English source)
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.