Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-68249: most: usb: hdm_probe: Fix calling put_device() before device initialization

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 3509c748e79435d09e730673c8c100b7f0ebc87c, 4af0eedbdb4df7936bf43a28e31af232744d2620, 6fb8fbc0aa542af5bf0fed94fa6b0edf18144f95.

Low priority for now. Upgrade to Linux Linux 3509c748e79435d09e730673c8c100b7f0ebc87c, 4af0eedbdb4df7936bf43a28e31af232744d2620, 6fb8fbc0aa542af5bf0fed94fa6b0edf18144f95 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: most: usb: hdm_probe: Fix calling put_device() before device initialization The early error path in hdm_probe() can jump to err_free_mdev before &mdev->dev has been initialized with device_initialize(). Calling put_device(&mdev->dev) there triggers a device core WARN and ends up invoking kref_put(&kobj->kref, kobject_release) on an uninitialized kobject. In this path the private struct was only kmalloc'ed and the intended release is effectively kfree(mdev) anyway, so free it directly instead of calling put_device() on an uninitialized device. This removes the WARNING and fixes the pre-initialization error path.

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

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

    • 5.9affected
    • 97a6f772f36b7f52bcfa56a581bbd2470cffe23d and later · before 3509c748e79435d09e730673c8c100b7f0ebc87caffected · git
    • 97a6f772f36b7f52bcfa56a581bbd2470cffe23d and later · before ad2be44882716dc3589fbc5572cc13f88ead6b24affected · git
    • 97a6f772f36b7f52bcfa56a581bbd2470cffe23d and later · before c400410fe0580dd6118ae8d60287ac9ce71a65fdaffected · git
    • 97a6f772f36b7f52bcfa56a581bbd2470cffe23d and later · before 6fb8fbc0aa542af5bf0fed94fa6b0edf18144f95affected · git
    • 97a6f772f36b7f52bcfa56a581bbd2470cffe23d and later · before 7d851f746067b8ee5bac9c262f326ace0a6ea253affected · git
    • 97a6f772f36b7f52bcfa56a581bbd2470cffe23d and later · before 4af0eedbdb4df7936bf43a28e31af232744d2620affected · git
    • 97a6f772f36b7f52bcfa56a581bbd2470cffe23d and later · before a8cc9e5fcb0e2eef21513a4fec888f5712cb8162affected · git
    • before 5.9not affected · semver
    • 5.10.246 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.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.158-16.1.158-1
Debian:13linuxbefore 6.12.57-16.12.57-1
Debian:14linuxbefore 6.17.6-16.17.6-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-68247Dec 16, 2025 · posix-timers: Plug potential memory leak in do_timer_create()
    0Monitor
  • ← EarlierCVE-2025-68248Dec 16, 2025 · vmw_balloon: indicate success when effectively deflating during migration
    0Monitor
  • Later →CVE-2025-68250Dec 16, 2025 · hung_task: fix warnings caused by unaligned lock pointers
    32Monitor

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 Linux3509c748e79435d09e730673c8c100b7f0ebc87cVendor (CNA)
Linux Linux4af0eedbdb4df7936bf43a28e31af232744d2620Vendor (CNA)
Linux Linux6fb8fbc0aa542af5bf0fed94fa6b0edf18144f95Vendor (CNA)
Linux Linux7d851f746067b8ee5bac9c262f326ace0a6ea253Vendor (CNA)
Linux Linuxa8cc9e5fcb0e2eef21513a4fec888f5712cb8162Vendor (CNA)
Linux Linuxad2be44882716dc3589fbc5572cc13f88ead6b24Vendor (CNA)
Linux Linuxc400410fe0580dd6118ae8d60287ac9ce71a65fdVendor (CNA)
debian:linux6.1.158-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.

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 (6 more)

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

All records