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-2026-93136

bus: mhi: ep: Fix device refcount leak in the error path of MHI device creation

Description

In the Linux kernel, the following vulnerability has been resolved: bus: mhi: ep: Fix device refcount leak in the error path of MHI device creation mhi_ep_create_device() takes one device reference for the UL channel and another for the DL channel after allocating the transfer device. These references are normally released by mhi_ep_destroy_device() before the device itself is removed. If dev_set_name() or device_add() fails, the error path currently drops only one reference. The remaining channel references keep the device from being released and leave the channels associated with a device that was never registered. Route both failures through a common unwind path that drops the DL channel reference, the UL channel reference, and the initial reference from device_initialize().

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 32 days 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: Received.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (11 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 297c77a0f27312b9a04696018c4cbd47926ca92b – < 8acc3813ab5015af73eeb74c9032443162f122d1
    • affected 297c77a0f27312b9a04696018c4cbd47926ca92b – < 51ddb831a36102fd0ea25f354935e49abce9f0a1
    • affected 297c77a0f27312b9a04696018c4cbd47926ca92b – < 4fae8fd4adc7f4765463ddeb1a5fad23936432f6
    • affected 297c77a0f27312b9a04696018c4cbd47926ca92b – < 5587e7871ce994bb079f97fe7e430d99627e5292
    • affected 297c77a0f27312b9a04696018c4cbd47926ca92b – < 8f3f64faee335eb678fd7dca7b95dfe3d0b271fd
    • affected 297c77a0f27312b9a04696018c4cbd47926ca92b – < 6f12862600bb70e599a614d706a095ea5f8f9858
  • Linux · Linux

    • affected 5.19
    • unaffected < 5.19
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .