CVE-2025-68249
Last modified
CVE-2025-68249 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
Description
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 97a6f772f36b7f52bcfa56a581bbd2470cffe23d, < 3509c748e79435d09e730673c8c100b7f0ebc87c; >= 97a6f772f36b7f52bcfa56a581bbd2470cffe23d, < ad2be44882716dc3589fbc5572cc13f88ead6b24; >= 97a6f772f36b7f52bcfa56a581bbd2470cffe23d, < c400410fe0580dd6118ae8d60287ac9ce71a65fd; >= 97a6f772f36b7f52bcfa56a581bbd2470cffe23d, < 6fb8fbc0aa542af5bf0fed94fa6b0edf18144f95; >= 97a6f772f36b7f52bcfa56a581bbd2470cffe23d, < 7d851f746067b8ee5bac9c262f326ace0a6ea253; >= 97a6f772f36b7f52bcfa56a581bbd2470cffe23d, < 4af0eedbdb4df7936bf43a28e31af232744d2620; >= 97a6f772f36b7f52bcfa56a581bbd2470cffe23d, < a8cc9e5fcb0e2eef21513a4fec888f5712cb8162 |
| Linux | Linux | 5.9 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2025-68249?
How severe is CVE-2025-68249?
How do I fix CVE-2025-68249?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-68243In the Linux kernel, the following vulnerability has been re…7
- CVE-2025-68244In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68245In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68246In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2025-68247In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68248In the Linux kernel, the following vulnerability has been re…
- CVE-2025-6825A vulnerability classified as critical was found in TOTOLINK…8.8
- CVE-2025-68250In the Linux kernel, the following vulnerability has been re…8.2
- CVE-2025-68251In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68252In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68253In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68254In the Linux kernel, the following vulnerability has been re…7.1
Are you affected by CVE-2025-68249?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
