Kernel warning via uninitialized device release
Published Dec 16, 2025 · Updated Dec 16, 2025
Resource-management error in the Linux kernel allows attackers to trigger a device-core warning via unspecified vectors. In drivers/most/most_usb.c, hdm_probe calls put_device() after an early error jump, before device_initialize() has initialized mdev->dev, causing kref_put() to act on an uninitialized kobject. The path requires a USB probe failure before initialization; public kernel materials do not establish attacker control, a crash, or another service interruption.
Summary
What happened
Resource-management error in the Linux kernel allows attackers to trigger a device-core warning via unspecified vectors. In drivers/most/most_usb.c, hdm_probe calls put_device() after an early error jump, before device_initialize() has initialized mdev->dev, causing kref_put() to act on an uninitialized kobject. The path requires a USB probe failure before initialization; public kernel materials do not establish attacker control, a crash, or another service interruption.
The record
- CVE
- CVE-2025-68249
- Published
- Dec 16, 2025
- Updated
- Dec 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 16, 2025CVE publishedPublication date reported by the CVE source.
- Dec 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.9
- Affected versionversion=97a6f772f36b7f52bcfa56a581bbd2470cffe23d <3509c748e79435d09e730673c8c100b7f0ebc87c
- Affected versionversion=97a6f772f36b7f52bcfa56a581bbd2470cffe23d <4af0eedbdb4df7936bf43a28e31af232744d2620
- Affected versionversion=97a6f772f36b7f52bcfa56a581bbd2470cffe23d <6fb8fbc0aa542af5bf0fed94fa6b0edf18144f95
- Affected versionversion=97a6f772f36b7f52bcfa56a581bbd2470cffe23d <7d851f746067b8ee5bac9c262f326ace0a6ea253
- Affected versionversion=97a6f772f36b7f52bcfa56a581bbd2470cffe23d <a8cc9e5fcb0e2eef21513a4fec888f5712cb8162
- Affected versionversion=97a6f772f36b7f52bcfa56a581bbd2470cffe23d <ad2be44882716dc3589fbc5572cc13f88ead6b24
- Affected versionversion=97a6f772f36b7f52bcfa56a581bbd2470cffe23d <c400410fe0580dd6118ae8d60287ac9ce71a65fd
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo