Skip to content
Noroxi
CVE-2025-68342· NVD / CVE Program· CNA Linux

can: gs_usb: gs_usb_receive_bulk_callback(): check actual_length before accessing data

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.18% (FIRST EPSS).
  • Fixed version: Linux Linux 395d988f93861101ec89d0dd9e3b876ae9392a5b, 4ffac725154cf6a253f5e6aa0c8946232b6a0af5, ad55004a3cb5b41ef78aa6c09e7bc5a489ba652b.

Low priority for now. Upgrade to Linux Linux 395d988f93861101ec89d0dd9e3b876ae9392a5b, 4ffac725154cf6a253f5e6aa0c8946232b6a0af5, ad55004a3cb5b41ef78aa6c09e7bc5a489ba652b 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(): check actual_length before accessing data The URB received in gs_usb_receive_bulk_callback() contains a struct gs_host_frame. The length of the data after the header depends on the gs_host_frame hf::flags and the active device features (e.g. time stamping). Introduce a new function gs_usb_get_minimum_length() and check that we have at least received the required amount of data before accessing it. Only copy the data to that skb that has actually been received. [mkl: rename gs_usb_get_minimum_length() -> +gs_usb_get_minimum_rx_length()]

—No exploit Fix available
Published
Dec 23, 2025
Updated
Oct 19, 2026
EPSS
0.1% · 7th 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.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.

Follow CVE-2025-68342

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

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack 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 (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

Running WordPress? Scan your site free with WP Lens

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 4ffac725154cf6a253f5e6aa0c8946232b6a0af5affected · git
    • d08e973a77d128b25e01a08c34d89593fdf222da and later · before ad55004a3cb5b41ef78aa6c09e7bc5a489ba652baffected · git
    • d08e973a77d128b25e01a08c34d89593fdf222da and later · before fb0c7c77a7ae3a2c3404b7d0173b8739a754b513affected · git
    • d08e973a77d128b25e01a08c34d89593fdf222da and later · before 395d988f93861101ec89d0dd9e3b876ae9392a5baffected · git
    • before 3.16not affected · semver
    • 6.6.119 and later · up to and including 6.6.*not affected · semver
    • 6.12.61 and later · up to and including 6.12.*not affected · semver
    • 6.17.11 and later · up to and including 6.17.*not affected · semver
    • 6.18 and laternot affected · original_commit_for_fix

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:13linuxbefore 6.12.63-16.12.63-1
Debian:14linuxbefore 6.17.11-16.17.11-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-2025-68339Dec 23, 2025 · atm/fore200e: Fix possible data race in fore200e_open()
    0Monitor
  • ← EarlierCVE-2025-68341Dec 23, 2025 · veth: reduce XDP no_direct return section to fix race
    39Monitor
  • Later →CVE-2025-68343Dec 23, 2025 · can: gs_usb: gs_usb_receive_bulk_callback(): check actual_length before accessing header
    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 Linux395d988f93861101ec89d0dd9e3b876ae9392a5bVendor (CNA)
Linux Linux4ffac725154cf6a253f5e6aa0c8946232b6a0af5Vendor (CNA)
Linux Linuxad55004a3cb5b41ef78aa6c09e7bc5a489ba652bVendor (CNA)
Linux Linuxfb0c7c77a7ae3a2c3404b7d0173b8739a754b513Vendor (CNA)
debian:linux6.12.63-1 · Debian:13Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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 researchers

Finders, 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

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.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

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

All records