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-23357can: mcp251x: fix deadlock in error path of mcp251x_open

Description

In the Linux kernel, the following vulnerability has been resolved: can: mcp251x: fix deadlock in error path of mcp251x_open The mcp251x_open() function call free_irq() in its error path with the mpc_lock mutex held. But if an interrupt already occurred the interrupt handler will be waiting for the mpc_lock and free_irq() will deadlock waiting for the handler to finish. This issue is similar to the one fixed in commit 7dd9c26bd6cf ("can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open") but for the error path. To solve this issue move the call to free_irq() after the lock is released. Setting `priv->force_quit = 1` beforehand ensure that the IRQ handler will exit right away once it acquired the lock.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 8 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-23357, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.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.11% · top 99% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
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 bf66f3736a945dd4e92d86427276c6eeab0a6c1d – < 739454057572cb0948658d1142f3fa2c6966465c
    • affected bf66f3736a945dd4e92d86427276c6eeab0a6c1d – < 416c18ecddafab0ed09be1e7b9d2f448f3d4db16
    • affected bf66f3736a945dd4e92d86427276c6eeab0a6c1d – < 256f0cff6e946c570392bda1d01a65e789a7afd0
    • affected bf66f3736a945dd4e92d86427276c6eeab0a6c1d – < b73832292cd914e87a55e863ba4413a907e7db6b
    • affected bf66f3736a945dd4e92d86427276c6eeab0a6c1d – < 38063cc435b69d56e76f947c10d336fcb2953508
    • affected bf66f3736a945dd4e92d86427276c6eeab0a6c1d – < d27f12c3f5e85efc479896af4a69eccb37f75e8e
    • affected bf66f3736a945dd4e92d86427276c6eeab0a6c1d – < e728f444c913a91d290d1824b4770780bbd6378e
    • affected bf66f3736a945dd4e92d86427276c6eeab0a6c1d – < ab3f894de216f4a62adc3b57e9191888cbf26885
  • Linux · Linux

    • affected 2.6.34
    • unaffected < 2.6.34
    • 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

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .