CVE-2026-23362

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: 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.

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: bcm: fix locking for bcm_op runtime updates - kernel/git/stable/linux.git - Linux kernel stable tree

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

can: bcm: fix locking for bcm_op runtime updates - kernel/git/stable/linux.git - Linux kernel stable tree

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

can: bcm: fix locking for bcm_op runtime updates - kernel/git/stable/linux.git - Linux kernel stable tree

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

can: bcm: fix locking for bcm_op runtime updates - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8bcf2d847adb82b2c617456f6da17ac5e6c75285
generic

can: bcm: fix locking for bcm_op runtime updates - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8215ba7bc99e84e66fd6938874ec4330a9d96518
generic

can: bcm: fix locking for bcm_op runtime updates - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/800f26f11ae37b17f58e0001f28a47dd75c26557
generic

can: bcm: fix locking for bcm_op runtime updates - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/70e951afad4c025261fe3c952d2b07237e320a01
generic

can: bcm: fix locking for bcm_op runtime updates - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0904037e713f787d1376e1d349c3bdf6c3105881

Vendor Advisories for CVE-2026-23362(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 (120 versions)6.19.8-1—

Weakness Classification(1)

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

All Vendor Advisories

(24)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 2× in last 7d / 21× 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 185 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-23362?
CVE-2026-23362 is a medium vulnerability published on March 25, 2026. 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 bcmop with a new…
When was CVE-2026-23362 disclosed?
CVE-2026-23362 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-23362 actively exploited?
CVE-2026-23362 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.3% of all scored CVEs.
What is the CVSS score of CVE-2026-23362?
CVE-2026-23362 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-23362?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23362, 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-23362

Explore →

Is Your Infrastructure Affected by CVE-2026-23362?

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

Start Free Scan →Browse All CVEs