CVE-2025-40223

most: usb: Fix use-after-free in hdm_disconnect

N/A
Published: December 4, 2025 at 03:31 PM UTC
Updated: October 19, 2026 at 07:10 PM 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: most: usb: Fix use-after-free in hdm_disconnect hdm_disconnect() calls most_deregister_interface(), which eventually unregisters the MOST interface device with device_unregister(iface->dev). If that drops the last reference, the device core may call release_mdev() immediately while hdm_disconnect() is still executing. The old code also freed several mdev-owned allocations in hdm_disconnect() and then performed additional put_device() calls. Depending on refcount order, this could lead to use-after-free or double-free when release_mdev() ran (or when unregister paths also performed puts). Fix by moving the frees of mdev-owned allocations into release_mdev(), so they happen exactly once when the device is truly released, and by dropping the extra put_device() calls in hdm_disconnect() that are redundant after device_unregister() and most_deregister_interface(). This addresses the KASAN slab-use-after-free reported by syzbot in hdm_disconnect(). See report and stack traces in the bug link below.

Affected

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

5.997a6f772f36b7f52bcfa56a581bbd2470cffe23d
Vendor states this is fixed in 33daf469f5294b9d07c4fc98216cace9f4f34cc6 (fixed)
Vendor states this is fixed in 3a3b8e89c7201c5b3b76ac4a4069d1adde1477d6 (fixed)
Vendor states this is fixed in 4b1270902609ef0d935ed2faa2ea6d122bd148f5 (fixed)
Vendor states this is fixed in 578eb18cd111addec94c43f61cd4b4429e454809 (fixed)
Vendor states this is fixed in 5b5c478f09b1b35e7fe6fc9a1786c9bf6030e831 (fixed)
Vendor states this is fixed in 72427dc6f87523995f4e6ae35a948bb2992cabce (fixed)
Vendor states this is fixed in f93a84ffb884d761a9d4e869ba29c238711e81f1 (fixed)
Vendor states this is fixed in 5.10.246 (unaffected)
Vendor states this is fixed in 5.15.196 (unaffected)
Vendor states this is fixed in 5.9 (unaffected)
Vendor states this is fixed in 6.1.158 (unaffected)
Vendor states this is fixed in 6.12.56 (unaffected)
Vendor states this is fixed in 6.17.6 (unaffected)
Vendor states this is fixed in 6.18 (unaffected)
Vendor states this is fixed in 6.6.115 (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

StatusDEFERRED

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