CVE-2026-23347: can: usb: f81604: correctly anchor the urb in the read bulk callback
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.13% (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 54ee74307165b348b2fddcd7942eb48fb4ee1237, 7724645c4792914cd07f36718816c5369cc57970, 952caa5da10bed22be09612433964f6877ba0dde; azl3 kernel 6.6.126.1-1 on Azure Linux 3.0 6.6.130.1-1.
Low priority for now. Upgrade to Linux Linux 54ee74307165b348b2fddcd7942eb48fb4ee1237, 7724645c4792914cd07f36718816c5369cc57970, 952caa5da10bed22be09612433964f6877ba0dde; azl3 kernel 6.6.126.1-1 on Azure Linux 3.0 6.6.130.1-1 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: usb: f81604: correctly anchor the urb in the read bulk callback When submitting an urb, that is using the anchor pattern, it needs to be anchored before submitting it otherwise it could be leaked if usb_kill_anchored_urbs() is called. This logic is correctly done elsewhere in the driver, except in the read bulk callback so do that here also.
- Published
- Mar 25, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
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.1%
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 kernel6.5.1 and later · before 6.6.130
- linux linux kernel6.7 and later · before 6.12.77
- linux linux kernel6.13 and later · before 6.18.17
- linux linux kernel6.19 and later · before 6.19.7
- linux linux kernel6.5
- 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
- 6.5affected
- 88da17436973e463bed59bea79771fb03a21555e and later · before 54ee74307165b348b2fddcd7942eb48fb4ee1237affected · git
- 88da17436973e463bed59bea79771fb03a21555e and later · before c001214e12202338425d6dda5d2a1919d674282daffected · git
- 88da17436973e463bed59bea79771fb03a21555e and later · before f6d80b104f904a6da922907394eec66d3e2ffc57affected · git
- 88da17436973e463bed59bea79771fb03a21555e and later · before 7724645c4792914cd07f36718816c5369cc57970affected · git
- 88da17436973e463bed59bea79771fb03a21555e and later · before 952caa5da10bed22be09612433964f6877ba0ddeaffected · git
- before 6.5not affected · semver
- 6.6.130 and later · up to and including 6.6.*not affected · semver
- 6.12.77 and later · up to and including 6.12.*not affected · semver
- 6.18.17 and later · up to and including 6.18.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| 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-23345Mar 25, 2026 · arm64: gcs: Do not set PTE_SHARED on GCS mappings if FEAT_LPA2 is enabled22Monitor
- ← EarlierCVE-2026-23346Mar 25, 2026 · arm64: io: Extract user memory type in ioremap_prot()22Monitor
- Later →CVE-2026-23348Mar 25, 2026 · cxl: Fix race of nvdimm_bus object when creating nvdimm objects18Monitor
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 | 54ee74307165b348b2fddcd7942eb48fb4ee1237 | Vendor (CNA) |
| Linux Linux | 7724645c4792914cd07f36718816c5369cc57970 | Vendor (CNA) |
| Linux Linux | 952caa5da10bed22be09612433964f6877ba0dde | Vendor (CNA) |
| Linux Linux | c001214e12202338425d6dda5d2a1919d674282d | Vendor (CNA) |
| Linux Linux | f6d80b104f904a6da922907394eec66d3e2ffc57 | Vendor (CNA) |
| azl3 kernel 6.6.126.1-1 on Azure Linux 3.0 | 6.6.130.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.12.85-1 · Debian:13 | 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)
—
CVSS 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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.