Strix
57.1K

CVE-2026-72119

HIGHCVSS 7.8/10EPSS 0.16%

Last modified

CVE-2026-72119 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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.. EPSS estimates a 0.16% chance of exploitation in the next 30 days.

Description

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.

Metrics

CVSS 3.1
7.8/10

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Probability
0.16%

6.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 7595de7bc56e0e52b74e56c90f7e247bf626d628, < a538b072ee074c9b41b9d9c15a6861a963e30755; >= fbd8fdc2b218e979cfe422b139b8f74c12419d1f, < 63422347b4c782f429748b2a09cd3cf3b77e6abd; >= 2a437b86ac5a9893c902f30ef66815bf13587bf6, < 37917e432e50b7de2b64230974380132a30f7270; >= 76c84c3728178b2d38d5604e399dfe8b0752645e, < 52f06e7603780de100233713ddaf971d422e10ef; >= cc55dd28c20a6611e30596019b3b2f636819a4c0, < 972fd66bb08fdef1090abe43196ca8da07216d13; >= c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7, < bd46f55dec608daa44b45dcf3328517630ad8e40; >= c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7, < 337f966c00662d81ad82cf5a4bbb150b2e32c0d4; >= c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7, < 12ce799f7ab1e05bd8fbf79e46f403bfe5597ebc; 8f1c022541bf5a923c8d6fa483112c15250f30a4; c4e8a172501e677ebd8ea9d9161d97dc4df56fbd; >= 5.10.238, < 5.10.265; >= 5.15.185, < 5.15.216; >= 6.1.141, < 6.1.183; >= 6.6.93, < 6.6.148; >= 6.12.31, < 6.12.101; >= 5.4.294, < 5.5; >= 6.14.9, < 6.15
LinuxLinux6.15

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is 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.
How severe is CVE-2026-72119?
CVE-2026-72119 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 0.16% probability of exploitation in the next 30 days.
How do I fix CVE-2026-72119?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-72119?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST