CVE-2026-72119

CVE CVE-2026-72119EUVD EUVD-2026-58877Published 2026-08-15T05:52:58.000ZLast changed 2026-08-19T16:36:13.000ZCVSS 7.8

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 6.12.31 <6.12.101; 5.15.185 <5.15.216; patch: 7.1.5; c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 <337f966c00662d81ad82cf5a4bbb150b2e32c0d4; 5.4.294 <5.5; patch: 6.12.101; c4e8a172501e677ebd8ea9d9161d97dc4df56fbd; 5.10.238 <5.10.265; 2a437b86ac5a9893c902f30ef66815bf13587bf6 <37917e432e50b7de2b64230974380132a30f7270; patch: 6.1.183; patch: 5.10.265; patch: 5.15.216; c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 <bd46f55dec608daa44b45dcf3328517630ad8e40; 7595de7bc56e0e52b74e56c90f7e247bf626d628 <a538b072ee074c9b41b9d9c15a6861a963e30755; 6.1.141 <6.1.183; cc55dd28c20a6611e30596019b3b2f636819a4c0 <972fd66bb08fdef1090abe43196ca8da07216d13; fbd8fdc2b218e979cfe422b139b8f74c12419d1f <63422347b4c782f429748b2a09cd3cf3b77e6abd; patch: 7.2; 6.14.9 <6.15; 76c84c3728178b2d38d5604e399dfe8b0752645e <52f06e7603780de100233713ddaf971d422e10ef; c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 <12ce799f7ab1e05bd8fbf79e46f403bfe5597ebc; 6.6.93 <6.6.148; 8f1c022541bf5a923c8d6fa483112c15250f30a4; 6.15; patch: 6.6.148; patch: 0; patch: 6.18.42

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.