CVE-2025-68249
CVE-2025-68249 is a security vulnerability that is still awaiting full analysis and scoring. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.
Key facts
- EPSS exploit prediction: 0% (7th percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2025-203647
- Published:
- Last modified:
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.
Frequently asked questions
- What is CVE-2025-68249?
- 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.
- Is CVE-2025-68249 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (7th percentile), an estimate of the probability of exploitation in the next 30 days.
- How do I fix CVE-2025-68249?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- Does CVE-2025-68249 have an EU (EUVD) identifier?
- Yes. CVE-2025-68249 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-203647.
- When was CVE-2025-68249 published?
- CVE-2025-68249 was published on 2025-12-16 and last updated on 2026-06-17.
References
- https://git.kernel.org/stable/c/3509c748e79435d09e730673c8c100b7f0ebc87c
- https://git.kernel.org/stable/c/4af0eedbdb4df7936bf43a28e31af232744d2620
- https://git.kernel.org/stable/c/6fb8fbc0aa542af5bf0fed94fa6b0edf18144f95
- https://git.kernel.org/stable/c/7d851f746067b8ee5bac9c262f326ace0a6ea253
- https://git.kernel.org/stable/c/a8cc9e5fcb0e2eef21513a4fec888f5712cb8162
- https://git.kernel.org/stable/c/ad2be44882716dc3589fbc5572cc13f88ead6b24
- https://git.kernel.org/stable/c/c400410fe0580dd6118ae8d60287ac9ce71a65fd