Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-23031: can: gs_usb: gs_usb_receive_bulk_callback(): fix URB memory leak

—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 0/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.22% (FIRST EPSS).
  • Fixed version: Linux Linux 08624b7206ddb9148eeffc2384ebda2c47b6d1e9, 7352e1d5932a0e777e39fa4b619801191f57e603, 9c151898cc259a7784be60ba38664f42ede39b31.

Low priority for now. Upgrade to Linux Linux 08624b7206ddb9148eeffc2384ebda2c47b6d1e9, 7352e1d5932a0e777e39fa4b619801191f57e603, 9c151898cc259a7784be60ba38664f42ede39b31 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: gs_usb: gs_usb_receive_bulk_callback(): fix URB memory leak In gs_can_open(), the URBs for USB-in transfers are allocated, added to the parent->rx_submitted anchor and submitted. In the complete callback gs_usb_receive_bulk_callback(), the URB is processed and resubmitted. In gs_can_close() the URBs are freed by calling usb_kill_anchored_urbs(parent->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 gs_can_close(). Fix the memory leak by anchoring the URB in the gs_usb_receive_bulk_callback() to the parent->rx_submitted anchor.

Published
Jan 31, 2026
Updated
Jun 17, 2026
EPSS
0.2% · 12th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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.

Follow CVE-2026-23031

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

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 help

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

—

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.16affected
    • d08e973a77d128b25e01a08c34d89593fdf222da and later · before 9c151898cc259a7784be60ba38664f42ede39b31affected · git
    • d08e973a77d128b25e01a08c34d89593fdf222da and later · before ec5ccc2af9e5b045671f3f604b57512feda8bcc5affected · git
    • d08e973a77d128b25e01a08c34d89593fdf222da and later · before f905bcfa971edb89e398c98957838d8c6381c0c7affected · git
    • d08e973a77d128b25e01a08c34d89593fdf222da and later · before 08624b7206ddb9148eeffc2384ebda2c47b6d1e9affected · git
    • d08e973a77d128b25e01a08c34d89593fdf222da and later · before 9f669a38ca70839229b7ba0f851820850a2fe1f7affected · git
    • d08e973a77d128b25e01a08c34d89593fdf222da and later · before 7352e1d5932a0e777e39fa4b619801191f57e603affected · git
    • before 3.16not affected · semver
    • 5.15.203 and later · up to and including 5.15.*not affected · semver
    • 6.1.162 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.162-16.1.162-1
Debian:13linuxbefore 6.12.69-16.12.69-1
Debian:14linuxbefore 6.18.8-16.18.8-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-23029Jan 31, 2026 · LoongArch: KVM: Fix kvm_device leak in kvm_eiointc_destroy()
    0Monitor
  • ← EarlierCVE-2026-23030Jan 31, 2026 · phy: rockchip: inno-usb2: Fix a double free bug in rockchip_usb2phy_probe()
    0Monitor
  • Later →CVE-2026-23032Jan 31, 2026 · null_blk: fix kmemleak by releasing references to fault configfs items
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux08624b7206ddb9148eeffc2384ebda2c47b6d1e9Vendor (CNA)
Linux Linux7352e1d5932a0e777e39fa4b619801191f57e603Vendor (CNA)
Linux Linux9c151898cc259a7784be60ba38664f42ede39b31Vendor (CNA)
Linux Linux9f669a38ca70839229b7ba0f851820850a2fe1f7Vendor (CNA)
Linux Linuxec5ccc2af9e5b045671f3f604b57512feda8bcc5Vendor (CNA)
Linux Linuxf905bcfa971edb89e398c98957838d8c6381c0c7Vendor (CNA)
debian:linux6.1.162-1 · Debian:12Package 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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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.

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records