CVE-2026-23108: can: usb_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak
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.15% (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 07e9373739c6388af9d99797cdb2e79dbbcbe92b, 59ff56992bba28051ad67cd8cc7b0edfe7280796, 60719661b4cbd7ffbed1a0e0fa3bbc82d8bd2be9.
Low priority for now. Upgrade to Linux Linux 07e9373739c6388af9d99797cdb2e79dbbcbe92b, 59ff56992bba28051ad67cd8cc7b0edfe7280796, 60719661b4cbd7ffbed1a0e0fa3bbc82d8bd2be9 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_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak Fix similar memory leak as in commit 7352e1d5932a ("can: gs_usb: gs_usb_receive_bulk_callback(): fix URB memory leak"). In usb_8dev_open() -> usb_8dev_start(), the URBs for USB-in transfers are allocated, added to the priv->rx_submitted anchor and submitted. In the complete callback usb_8dev_read_bulk_callback(), the URBs are processed and resubmitted. In usb_8dev_close() -> unlink_all_urbs() the URBs are freed by calling usb_kill_anchored_urbs(&priv->rx_submitted). However, this does not take into account that the USB framework unanchors the URB before the complete function is called. This means that once an in-URB has been completed, it is no longer anchored and is ultimately not released in usb_kill_anchored_urbs(). Fix the memory leak by anchoring the URB in the usb_8dev_read_bulk_callback() to the priv->rx_submitted anchor.
- Published
- Feb 4, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-401
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%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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.
Is your version affected? Check itNoroxi 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 kernel3.9 and later · before 5.10.249
- linux linux kernel5.11 and later · before 5.15.199
- linux linux kernel5.16 and later · before 6.1.162
- linux linux kernel6.2 and later · before 6.6.122
- linux linux kernel6.7 and later · before 6.12.68
- linux linux kernel6.13 and later · before 6.18.8
- linux linux kernel6.19
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
- 3.9affected
- 0024d8ad1639e32d717445c69ca813fd19c2a91c and later · before feb8243eaea7efd5279b19667d7189fd8654c87aaffected · git
- 0024d8ad1639e32d717445c69ca813fd19c2a91c and later · before ef6e608e5ee71eca0cd3475c737e684cef24f240affected · git
- 0024d8ad1639e32d717445c69ca813fd19c2a91c and later · before 60719661b4cbd7ffbed1a0e0fa3bbc82d8bd2be9affected · git
- 0024d8ad1639e32d717445c69ca813fd19c2a91c and later · before 59ff56992bba28051ad67cd8cc7b0edfe7280796affected · git
- 0024d8ad1639e32d717445c69ca813fd19c2a91c and later · before ea4a98e924164586066b39f29bfcc7cc9da108cdaffected · git
- 0024d8ad1639e32d717445c69ca813fd19c2a91c and later · before 07e9373739c6388af9d99797cdb2e79dbbcbe92baffected · git
- 0024d8ad1639e32d717445c69ca813fd19c2a91c and later · before f7a980b3b8f80fe367f679da376cf76e800f9480affected · git
- before 3.9not affected · semver
- 5.10.249 and later · up to and including 5.10.*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:12 | linux | before 6.1.162-1 | 6.1.162-1 |
| Debian:13 | linux | before 6.12.69-1 | 6.12.69-1 |
| Debian:14 | linux | before 6.18.8-1 | 6.18.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-23105Feb 4, 2026 · net/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag22Monitor
- ← EarlierCVE-2026-23107Feb 4, 2026 · arm64/fpsimd: signal: Allocate SSVE storage when restoring ZA22Monitor
- Later →CVE-2026-23110Feb 4, 2026 · scsi: core: Wake up the error handler when final completions race against each other18Monitor
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 | 07e9373739c6388af9d99797cdb2e79dbbcbe92b | Vendor (CNA) |
| Linux Linux | 59ff56992bba28051ad67cd8cc7b0edfe7280796 | Vendor (CNA) |
| Linux Linux | 60719661b4cbd7ffbed1a0e0fa3bbc82d8bd2be9 | Vendor (CNA) |
| Linux Linux | ea4a98e924164586066b39f29bfcc7cc9da108cd | Vendor (CNA) |
| Linux Linux | ef6e608e5ee71eca0cd3475c737e684cef24f240 | Vendor (CNA) |
| Linux Linux | f7a980b3b8f80fe367f679da376cf76e800f9480 | Vendor (CNA) |
| Linux Linux | feb8243eaea7efd5279b19667d7189fd8654c87a | Vendor (CNA) |
| debian:linux | 6.1.162-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-401 · Missing Release of Memory after Effective LifetimeCVSS 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 (6 more)Show less
- git.kernel.org/stable/c/59ff56992bba28051ad67cd8cc7b0edfe7280796
- git.kernel.org/stable/c/60719661b4cbd7ffbed1a0e0fa3bbc82d8bd2be9
- git.kernel.org/stable/c/ea4a98e924164586066b39f29bfcc7cc9da108cd
- git.kernel.org/stable/c/ef6e608e5ee71eca0cd3475c737e684cef24f240
- git.kernel.org/stable/c/f7a980b3b8f80fe367f679da376cf76e800f9480
- git.kernel.org/stable/c/feb8243eaea7efd5279b19667d7189fd8654c87a
Vendor advisories and official records. Exploit/PoC links are deliberately left out.