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.
Affected versions
Linux kernel versions
5.9
and later are affected. Fixed in
5.10.246,
5.15.196,
6.1.158,
6.6.115,
6.12.56,
6.17.6,
6.18
and their respective stable series.
References
The following references provide additional information about CVE-2025-68249 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.
-
PatchKernel patch commithttps://git.kernel.org/stable/c/3509c748e79435d09e730673c8c100b7f0ebc87c
-
PatchKernel patch commithttps://git.kernel.org/stable/c/4af0eedbdb4df7936bf43a28e31af232744d2620
-
PatchKernel patch commithttps://git.kernel.org/stable/c/6fb8fbc0aa542af5bf0fed94fa6b0edf18144f95
Frequently asked questions
-
What is CVE-2025-68249?
CVE-2025-68249 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 5.9 onward and has been patched in 5.10.246, 5.15.196, 6.1.158 and others. CVE-2025-68249 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2025-68249?
Yes — CVE-2025-68249 has been patched. Fixed versions include 5.10.246, 5.15.196, 6.1.158 and others. If you are running Linux kernel 5.9 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2025-68249 actively exploited?
No — CVE-2025-68249 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.