Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-68312: usbnet: Prevents free active kevent

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.19% (FIRST EPSS).
  • Fixed version: Linux Linux 285d4b953f2ca03c358f986718dd89ee9bde632e, 2ce1de32e05445d77fc056f6ff8339cfb78a5f84, 3a10619fdefd3051aeb14860e4d4335529b4e94d.

Low priority for now. Upgrade to Linux Linux 285d4b953f2ca03c358f986718dd89ee9bde632e, 2ce1de32e05445d77fc056f6ff8339cfb78a5f84, 3a10619fdefd3051aeb14860e4d4335529b4e94d 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: usbnet: Prevents free active kevent The root cause of this issue are: 1. When probing the usbnet device, executing usbnet_link_change(dev, 0, 0); put the kevent work in global workqueue. However, the kevent has not yet been scheduled when the usbnet device is unregistered. Therefore, executing free_netdev() results in the "free active object (kevent)" error reported here. 2. Another factor is that when calling usbnet_disconnect()->unregister_netdev(), if the usbnet device is up, ndo_stop() is executed to cancel the kevent. However, because the device is not up, ndo_stop() is not executed. The solution to this problem is to cancel the kevent before executing free_netdev().

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

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.

Follow CVE-2025-68312

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

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

    • d2d6b530d89b0a912148018027386aa049f0a309, e2a521a7dcc463c5017b4426ca0804e151faeff7, 7f77dcbc030c2faa6d8e8a594985eeb34018409e, d49bb8cf9bfaa06aa527eb30f1a52a071da2e32f, db3b738ae5f726204876f4303c49cfdf4311403f, 6.0affected
    • 8b4588b8b00b299be16a35be67b331d8fdba03f3 and later · before 285d4b953f2ca03c358f986718dd89ee9bde632eaffected · git
    • 135199a2edd459d2b123144efcd7f9bcd95128e4 and later · before 88a38b135d69f5db9024ff6527232f1b51be8915affected · git
    • 635fd8953e4309b54ca6a81bed1d4a87668694f4 and later · before 43005002b60ef3424719ecda16d124714b45da3baffected · git
    • a69e617e533edddf3fa3123149900f36e0a6dc74 and later · before 3a10619fdefd3051aeb14860e4d4335529b4e94daffected · git
    • a69e617e533edddf3fa3123149900f36e0a6dc74 and later · before 9a579d6a39513069d298eee70770bbac8a148565affected · git
    • a69e617e533edddf3fa3123149900f36e0a6dc74 and later · before 2ce1de32e05445d77fc056f6ff8339cfb78a5f84affected · git
    • a69e617e533edddf3fa3123149900f36e0a6dc74 and later · before 5158fb8da162e3982940f30cd01ed77bdf42c6fcaffected · git
    • a69e617e533edddf3fa3123149900f36e0a6dc74 and later · before 420c84c330d1688b8c764479e5738bbdbf0a33deaffected · git
    • 5.4.211 and later · before 5.4.302affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.159-16.1.159-1
Debian:13linuxbefore 6.12.63-16.12.63-1
Debian:14linuxbefore 6.17.8-16.17.8-1
SUSE:Linux Enterprise Micro 5.2kernel-defaultbefore 5.3.18-150300.59.235.15.3.18-150300.59.235.1
SUSE:Linux Enterprise Micro 5.2kernel-default-basebefore 5.3.18-150300.59.235.1.150300.18.140.15.3.18-150300.59.235.1.150300.18.140.1
SUSE:Linux Enterprise Micro 5.2kernel-rtbefore 5.3.18-150300.235.15.3.18-150300.235.1
SUSE:Linux Enterprise Micro 5.2kernel-source-rtbefore 5.3.18-150300.235.15.3.18-150300.235.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-68309Dec 16, 2025 · PCI/AER: Fix NULL pointer access by aer_info
    0Monitor
  • ← EarlierCVE-2025-68311Dec 16, 2025 · tty: serial: ip22zilog: Use platform device for probing
    0Monitor
  • Later →CVE-2025-68313Dec 16, 2025 · x86/CPU/AMD: Add RDSEED fix for Zen5
    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 / packageFixed versionSource
Linux Linux285d4b953f2ca03c358f986718dd89ee9bde632eVendor (CNA)
Linux Linux2ce1de32e05445d77fc056f6ff8339cfb78a5f84Vendor (CNA)
Linux Linux3a10619fdefd3051aeb14860e4d4335529b4e94dVendor (CNA)
Linux Linux4.10Vendor (CNA)
Linux Linux4.15Vendor (CNA)
Linux Linux4.20Vendor (CNA)
Linux Linux420c84c330d1688b8c764479e5738bbdbf0a33deVendor (CNA)
Linux Linux43005002b60ef3424719ecda16d124714b45da3bVendor (CNA)
Linux Linux5.10.247Vendor (CNA)
Linux Linux5.15.197Vendor (CNA)
Linux Linux5.19Vendor (CNA)
Linux Linux5.20Vendor (CNA)
Linux Linux5.4.302Vendor (CNA)
Linux Linux5158fb8da162e3982940f30cd01ed77bdf42c6fcVendor (CNA)
Linux Linux88a38b135d69f5db9024ff6527232f1b51be8915Vendor (CNA)
Linux Linux9a579d6a39513069d298eee70770bbac8a148565Vendor (CNA)
debian:linux6.1.159-1 · Debian:12Package registry (OSV)
suse:kernel-default5.3.18-150300.59.235.1 · SUSE:Linux Enterprise Micro 5.2Package registry (OSV)
suse:kernel-default-base5.3.18-150300.59.235.1.150300.18.140.1 · SUSE:Linux Enterprise Micro 5.2Package registry (OSV)
suse:kernel-rt5.3.18-150300.235.1 · SUSE:Linux Enterprise Micro 5.2Package registry (OSV)
suse:kernel-source-rt5.3.18-150300.235.1 · SUSE:Linux Enterprise Micro 5.2Package 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 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 (7 more)

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

All records