CVE-2026-23362: can: bcm: fix locking for bcm_op runtime updates
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.09% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0904037e713f787d1376e1d349c3bdf6c3105881, 5.10.253, 5.15.203; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 0904037e713f787d1376e1d349c3bdf6c3105881, 5.10.253, 5.15.203; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 25, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.0% · 0th percentile
- CWE
- CWE-667
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.0%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.4.294 and later · before 5.5
- linux linux kernel5.10.238 and later · before 5.10.253
- linux linux kernel5.15.185 and later · before 5.15.203
- linux linux kernel6.1.141 and later · before 6.1.167
- linux linux kernel6.6.93 and later · before 6.6.130
- linux linux kernel6.12.31 and later · before 6.12.77
- linux linux kernel6.14.9 and later · before 6.15
- linux linux kernel6.15.1 and later · before 6.18.17
- linux linux kernel6.19 and later · before 6.19.7
- linux linux kernel6.15
- linux linux kernel7.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 8f1c022541bf5a923c8d6fa483112c15250f30a4, c4e8a172501e677ebd8ea9d9161d97dc4df56fbd, 6.15affected
- 7595de7bc56e0e52b74e56c90f7e247bf626d628 and later · before 0904037e713f787d1376e1d349c3bdf6c3105881affected · git
- fbd8fdc2b218e979cfe422b139b8f74c12419d1f and later · before c85b96eaf766d8f066b1139a17a51efa2f6627efaffected · git
- 2a437b86ac5a9893c902f30ef66815bf13587bf6 and later · before 800f26f11ae37b17f58e0001f28a47dd75c26557affected · git
- 76c84c3728178b2d38d5604e399dfe8b0752645e and later · before 70e951afad4c025261fe3c952d2b07237e320a01affected · git
- cc55dd28c20a6611e30596019b3b2f636819a4c0 and later · before 8bcf2d847adb82b2c617456f6da17ac5e6c75285affected · git
- c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 and later · before 8215ba7bc99e84e66fd6938874ec4330a9d96518affected · git
- c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 and later · before f0c349b2c21b220af5ba19f29b885e222958d796affected · git
- c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 and later · before c35636e91e392e1540949bbc67932167cb48bc3aaffected · git
- 5.10.238 and later · before 5.10.253affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.170-1 | 6.1.170-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.8-1 | 6.19.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-23358Mar 25, 2026 · drm/amdgpu: Fix error handling in slot reset22Monitor
- ← EarlierCVE-2026-23360Mar 25, 2026 · nvme: fix admin queue leak on controller reset22Monitor
- Later →CVE-2026-23363Mar 25, 2026 · wifi: mt76: mt7925: Fix possible oob access in mt7925_mac_write_txwi_80211()28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0904037e713f787d1376e1d349c3bdf6c3105881 | Vendor (CNA) |
| Linux Linux | 5.10.253 | Vendor (CNA) |
| Linux Linux | 5.15.203 | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 6.1.167 | Vendor (CNA) |
| Linux Linux | 6.12.77 | Vendor (CNA) |
| Linux Linux | 6.15 | Vendor (CNA) |
| Linux Linux | 6.6.130 | Vendor (CNA) |
| Linux Linux | 70e951afad4c025261fe3c952d2b07237e320a01 | Vendor (CNA) |
| Linux Linux | 800f26f11ae37b17f58e0001f28a47dd75c26557 | Vendor (CNA) |
| Linux Linux | 8215ba7bc99e84e66fd6938874ec4330a9d96518 | Vendor (CNA) |
| Linux Linux | 8bcf2d847adb82b2c617456f6da17ac5e6c75285 | Vendor (CNA) |
| Linux Linux | c35636e91e392e1540949bbc67932167cb48bc3a | Vendor (CNA) |
| Linux Linux | c85b96eaf766d8f066b1139a17a51efa2f6627ef | Vendor (CNA) |
| Linux Linux | f0c349b2c21b220af5ba19f29b885e222958d796 | Vendor (CNA) |
| cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.170-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-667 · Improper LockingCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/70e951afad4c025261fe3c952d2b07237e320a01
- git.kernel.org/stable/c/800f26f11ae37b17f58e0001f28a47dd75c26557
- git.kernel.org/stable/c/8215ba7bc99e84e66fd6938874ec4330a9d96518
- git.kernel.org/stable/c/8bcf2d847adb82b2c617456f6da17ac5e6c75285
- git.kernel.org/stable/c/c35636e91e392e1540949bbc67932167cb48bc3a
- git.kernel.org/stable/c/c85b96eaf766d8f066b1139a17a51efa2f6627ef
- git.kernel.org/stable/c/f0c349b2c21b220af5ba19f29b885e222958d796
Vendor advisories and official records. Exploit/PoC links are deliberately left out.