CVE-2026-72119
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.
Affected versions
Linux kernel versions
6.6.93,
6.12.31,
5.4.294,
5.10.238,
5.15.185,
6.1.141,
6.14.9,
6.15
and later are affected. Fixed in
6.6.148,
6.12.101,
6.18.42,
7.1.5,
7.2-rc4
and their respective stable series.
References
5 totalFrequently asked questions
-
What is CVE-2026-72119?
CVE-2026-72119 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 6.6.93 onward and has been patched in 6.6.148, 6.12.101, 6.18.42 and others. CVE-2026-72119 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-72119?
Yes. CVE-2026-72119 has been patched. Fixed versions include 6.6.148, 6.12.101, 6.18.42 and others. If you are running Linux kernel 6.6.93 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-72119 actively exploited?
No. CVE-2026-72119 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.