CVE-2026-23357

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-03-25. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

March 25, 2026

Last Modified

June 17, 2026

Advisory Details (8)

Auto-updated Aug 6, 2026
No patch confirmed yet.
generic

can: mcp251x: fix deadlock in error path of mcp251x_open - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e728f444c913a91d290d1824b4770780bbd6378e
generic

can: mcp251x: fix deadlock in error path of mcp251x_open - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d27f12c3f5e85efc479896af4a69eccb37f75e8e
generic

can: mcp251x: fix deadlock in error path of mcp251x_open - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b73832292cd914e87a55e863ba4413a907e7db6b
generic

can: mcp251x: fix deadlock in error path of mcp251x_open - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ab3f894de216f4a62adc3b57e9191888cbf26885
generic

can: mcp251x: fix deadlock in error path of mcp251x_open - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/739454057572cb0948658d1142f3fa2c6966465c
generic

can: mcp251x: fix deadlock in error path of mcp251x_open - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/416c18ecddafab0ed09be1e7b9d2f448f3d4db16
generic

can: mcp251x: fix deadlock in error path of mcp251x_open - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/38063cc435b69d56e76f947c10d336fcb2953508
generic

can: mcp251x: fix deadlock in error path of mcp251x_open - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/256f0cff6e946c570392bda1d01a65e789a7afd0

Vendor Advisories for CVE-2026-23357(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.253—osv
linuxKernel @ 6.1.167—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (117 versions)6.19.8-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 42× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 179 total refreshes for this CVE.

  1. 2026-09-02 15:01 UTCOSV refresh
  2. 2026-09-02 14:11 UTCEPSS rescore
  3. 2026-09-01 13:53 UTCEPSS rescore
  4. 2026-09-01 04:39 UTCEPSS rescore
  5. 2026-08-30 19:17 UTCEPSS rescore
  6. 2026-08-28 21:41 UTCEPSS rescore
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-21 23:49 UTCEPSS rescore
  11. 2026-08-20 22:55 UTCEPSS rescore
  12. 2026-08-19 17:03 UTCEPSS rescore
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 10:24 UTCEG score recompute
  16. 2026-08-16 10:24 UTCVendor advisory
  17. 2026-08-16 10:24 UTCGHSA enrichment
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 06:43 UTCEG score recompute
  20. 2026-08-14 06:43 UTCVendor advisory
  21. 2026-08-14 06:43 UTCGHSA enrichment
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-12 20:58 UTCEG score recompute
  24. 2026-08-12 20:58 UTCVendor advisory
  25. 2026-08-12 20:58 UTCGHSA enrichment
Show 75 more
  1. 2026-08-12 13:50 UTCEPSS rescore
  2. 2026-08-11 04:04 UTCEG score recompute
  3. 2026-08-11 04:04 UTCVendor advisory
  4. 2026-08-11 04:04 UTCGHSA enrichment
  5. 2026-08-11 00:00 UTCEPSS rescore
  6. 2026-08-10 05:11 UTCEG score recompute
  7. 2026-08-10 05:11 UTCVendor advisory
  8. 2026-08-10 05:11 UTCGHSA enrichment
  9. 2026-08-09 13:46 UTCEPSS rescore
  10. 2026-08-09 06:18 UTCEG score recompute
  11. 2026-08-09 06:18 UTCVendor advisory
  12. 2026-08-09 06:18 UTCGHSA enrichment
  13. 2026-08-08 16:37 UTCEPSS rescore
  14. 2026-08-07 16:35 UTCEG score recompute
  15. 2026-08-07 16:35 UTCVendor advisory
  16. 2026-08-07 16:35 UTCGHSA enrichment
  17. 2026-08-06 13:46 UTCEPSS rescore
  18. 2026-08-06 01:05 UTCEG score recompute
  19. 2026-08-06 01:05 UTCVendor advisory
  20. 2026-08-06 01:05 UTCGHSA enrichment
  21. 2026-08-05 19:17 UTCEPSS rescore
  22. 2026-08-04 15:10 UTCEPSS rescore
  23. 2026-08-04 10:38 UTCEPSS rescore
  24. 2026-08-03 23:50 UTCEG score recompute
  25. 2026-08-03 23:50 UTCVendor advisory
  26. 2026-08-03 23:50 UTCGHSA enrichment
  27. 2026-08-03 10:35 UTCEPSS rescore
  28. 2026-08-02 15:38 UTCEG score recompute
  29. 2026-08-02 15:38 UTCVendor advisory
  30. 2026-08-02 15:38 UTCGHSA enrichment
  31. 2026-08-01 04:15 UTCEPSS rescore
  32. 2026-07-30 01:30 UTCEPSS rescore
  33. 2026-07-27 14:13 UTCEPSS rescore
  34. 2026-07-25 14:17 UTCEPSS rescore
  35. 2026-07-25 14:17 UTCEPSS rescore
  36. 2026-07-24 14:17 UTCEPSS rescore
  37. 2026-07-23 14:18 UTCEPSS rescore
  38. 2026-07-23 14:18 UTCEPSS rescore
  39. 2026-07-23 03:07 UTCEG score recompute
  40. 2026-07-22 14:08 UTCEPSS rescore
  41. 2026-07-21 15:24 UTCEPSS rescore
  42. 2026-07-21 15:24 UTCEPSS rescore
  43. 2026-07-20 17:08 UTCEPSS rescore
  44. 2026-07-19 14:31 UTCEPSS rescore
  45. 2026-07-19 14:31 UTCEPSS rescore
  46. 2026-07-19 02:29 UTCEPSS rescore
  47. 2026-07-19 02:28 UTCEPSS rescore
  48. 2026-07-17 07:16 UTCOSV refresh
  49. 2026-07-16 17:03 UTCEPSS rescore
  50. 2026-07-16 17:03 UTCEPSS rescore
  51. 2026-07-15 16:57 UTCEPSS rescore
  52. 2026-07-15 16:57 UTCEPSS rescore
  53. 2026-07-15 02:00 UTCEPSS rescore
  54. 2026-07-15 02:00 UTCEPSS rescore
  55. 2026-07-13 06:13 UTCEPSS rescore
  56. 2026-07-13 06:13 UTCEPSS rescore
  57. 2026-07-12 05:46 UTCEPSS rescore
  58. 2026-07-12 05:46 UTCEPSS rescore
  59. 2026-07-09 19:10 UTCEPSS rescore
  60. 2026-07-08 15:15 UTCEPSS rescore
  61. 2026-07-08 15:15 UTCEPSS rescore
  62. 2026-07-06 16:27 UTCEPSS rescore
  63. 2026-07-06 16:27 UTCEPSS rescore
  64. 2026-07-06 02:23 UTCEPSS rescore
  65. 2026-07-06 02:23 UTCEPSS rescore
  66. 2026-07-05 02:30 UTCEPSS rescore
  67. 2026-07-04 06:31 UTCEPSS rescore
  68. 2026-07-04 06:31 UTCEPSS rescore
  69. 2026-07-01 15:06 UTCEPSS rescore
  70. 2026-07-01 15:06 UTCEPSS rescore
  71. 2026-06-30 23:22 UTCEPSS rescore
  72. 2026-06-30 23:22 UTCEPSS rescore
  73. 2026-06-29 14:06 UTCEPSS rescore
  74. 2026-06-29 05:02 UTCOSV refresh
  75. 2026-06-28 14:07 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-23357?
CVE-2026-23357 is a medium vulnerability published on March 25, 2026. In the Linux kernel, the following vulnerability has been resolved: can: mcp251x: fix deadlock in error path of mcp251x_open The mcp251xopen() function call freeirq() in its error path with the mpc_lock mutex held. But if an interrupt already occurred the interrupt handler will be waiting for the…
When was CVE-2026-23357 disclosed?
CVE-2026-23357 was first published in the National Vulnerability Database on March 25, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23357 actively exploited?
CVE-2026-23357 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.1% of all scored CVEs.
What is the CVSS score of CVE-2026-23357?
CVE-2026-23357 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-23357?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23357, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-23357

Explore →

Is Your Infrastructure Affected by CVE-2026-23357?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs