Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-72119can: bcm: extend bcm_tx_lock usage for data and timer updates

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-72119, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (20 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 7595de7bc56e0e52b74e56c90f7e247bf626d628 – < a538b072ee074c9b41b9d9c15a6861a963e30755
    • affected fbd8fdc2b218e979cfe422b139b8f74c12419d1f – < 63422347b4c782f429748b2a09cd3cf3b77e6abd
    • affected 2a437b86ac5a9893c902f30ef66815bf13587bf6 – < 37917e432e50b7de2b64230974380132a30f7270
    • affected 76c84c3728178b2d38d5604e399dfe8b0752645e – < 52f06e7603780de100233713ddaf971d422e10ef
    • affected cc55dd28c20a6611e30596019b3b2f636819a4c0 – < 972fd66bb08fdef1090abe43196ca8da07216d13
    • affected c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 – < bd46f55dec608daa44b45dcf3328517630ad8e40
    • affected c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 – < 337f966c00662d81ad82cf5a4bbb150b2e32c0d4
    • affected c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 – < 12ce799f7ab1e05bd8fbf79e46f403bfe5597ebc
    • affected 8f1c022541bf5a923c8d6fa483112c15250f30a4
    • affected c4e8a172501e677ebd8ea9d9161d97dc4df56fbd
    • affected 5.10.238 – < 5.10.265
    • affected 5.15.185 – < 5.15.216
    • affected 6.1.141 – < 6.1.183
    • affected 6.6.93 – < 6.6.148
    • affected 6.12.31 – < 6.12.101
    • affected 5.4.294 – < 5.5
    • affected 6.14.9 – < 6.15
  • Linux · Linux

    • affected 6.15
    • unaffected < 6.15
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-72119 badge
[![CVE-2026-72119](https://cveledger.app/badge/CVE-2026-72119.svg)](https://cveledger.app/cve/CVE-2026-72119)

Record last updated .