CVE-2026-93136

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

N/A
Published: September 17, 2026 at 04:11 PM UTC
Updated: October 19, 2026 at 10:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

297c77a0f27312b9a04696018c4cbd47926ca92b5.19
Vendor states this is fixed in 4fae8fd4adc7f4765463ddeb1a5fad23936432f6 (fixed)
Vendor states this is fixed in 51ddb831a36102fd0ea25f354935e49abce9f0a1 (fixed)
Vendor states this is fixed in 5587e7871ce994bb079f97fe7e430d99627e5292 (fixed)
Vendor states this is fixed in 6f12862600bb70e599a614d706a095ea5f8f9858 (fixed)
Vendor states this is fixed in 8acc3813ab5015af73eeb74c9032443162f122d1 (fixed)
Vendor states this is fixed in 8f3f64faee335eb678fd7dca7b95dfe3d0b271fd (fixed)
Vendor states this is fixed in 5.19 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card