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-23362can: bcm: fix locking for bcm_op runtime updates

Description

In the Linux kernel, the following vulnerability has been resolved: can: bcm: fix locking for bcm_op runtime updates Commit c2aba69d0c36 ("can: bcm: add locking for bcm_op runtime updates") added a locking for some variables that can be modified at runtime when updating the sending bcm_op with a new TX_SETUP command in bcm_tx_setup(). Usually the RX_SETUP only handles and filters incoming traffic with one exception: When the RX_RTR_FRAME flag is set a predefined CAN frame is sent when a specific RTR frame is received. Therefore the rx bcm_op uses bcm_can_tx() which uses the bcm_tx_lock that was only initialized in bcm_tx_setup(). Add the missing spin_lock_init() when allocating the bcm_op in bcm_rx_setup() to handle the RTR case properly.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 59 days 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-23362, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.10% · top 99% of all CVEs (15 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 7595de7bc56e0e52b74e56c90f7e247bf626d628 – < 0904037e713f787d1376e1d349c3bdf6c3105881
    • affected fbd8fdc2b218e979cfe422b139b8f74c12419d1f – < c85b96eaf766d8f066b1139a17a51efa2f6627ef
    • affected 2a437b86ac5a9893c902f30ef66815bf13587bf6 – < 800f26f11ae37b17f58e0001f28a47dd75c26557
    • affected 76c84c3728178b2d38d5604e399dfe8b0752645e – < 70e951afad4c025261fe3c952d2b07237e320a01
    • affected cc55dd28c20a6611e30596019b3b2f636819a4c0 – < 8bcf2d847adb82b2c617456f6da17ac5e6c75285
    • affected c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 – < 8215ba7bc99e84e66fd6938874ec4330a9d96518
    • affected c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 – < f0c349b2c21b220af5ba19f29b885e222958d796
    • affected c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 – < c35636e91e392e1540949bbc67932167cb48bc3a
    • affected 8f1c022541bf5a923c8d6fa483112c15250f30a4
    • affected c4e8a172501e677ebd8ea9d9161d97dc4df56fbd
    • affected 5.10.238 – < 5.10.253
    • affected 5.15.185 – < 5.15.203
    • affected 6.1.141 – < 6.1.167
    • affected 6.6.93 – < 6.6.130
    • affected 6.12.31 – < 6.12.77
    • affected 5.4.294 – < 5.5
    • affected 6.14.9 – < 6.15
  • Linux · Linux

    • affected 6.15
    • unaffected < 6.15
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.167 – ≤ 6.1.*
    • unaffected 6.6.130 – ≤ 6.6.*
    • unaffected 6.12.77 – ≤ 6.12.*
    • unaffected 6.18.17 – ≤ 6.18.*
    • unaffected 6.19.7 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .