Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.19% · top 91% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 97a6f772f36b7f52bcfa56a581bbd2470cffe23d – < 3509c748e79435d09e730673c8c100b7f0ebc87c
    • affected 97a6f772f36b7f52bcfa56a581bbd2470cffe23d – < ad2be44882716dc3589fbc5572cc13f88ead6b24
    • affected 97a6f772f36b7f52bcfa56a581bbd2470cffe23d – < c400410fe0580dd6118ae8d60287ac9ce71a65fd
    • affected 97a6f772f36b7f52bcfa56a581bbd2470cffe23d – < 6fb8fbc0aa542af5bf0fed94fa6b0edf18144f95
    • affected 97a6f772f36b7f52bcfa56a581bbd2470cffe23d – < 7d851f746067b8ee5bac9c262f326ace0a6ea253
    • affected 97a6f772f36b7f52bcfa56a581bbd2470cffe23d – < 4af0eedbdb4df7936bf43a28e31af232744d2620
    • affected 97a6f772f36b7f52bcfa56a581bbd2470cffe23d – < a8cc9e5fcb0e2eef21513a4fec888f5712cb8162
  • Linux · Linux

    • affected 5.9
    • unaffected < 5.9
    • unaffected 5.10.246 – ≤ 5.10.*
    • unaffected 5.15.196 – ≤ 5.15.*
    • unaffected 6.1.158 – ≤ 6.1.*
    • unaffected 6.6.115 – ≤ 6.6.*
    • unaffected 6.12.56 – ≤ 6.12.*
    • unaffected 6.17.6 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-68249 badge
[![CVE-2025-68249](https://cveledger.app/badge/CVE-2025-68249.svg)](https://cveledger.app/cve/CVE-2025-68249)

Record last updated .